IRC logs of #tryton for Saturday, 2016-07-02

chat.freenode.net #tryton log beginning Sat Jul 2 00:00:01 CEST 2016
-!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton01:01
-!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton01:44
-!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton02:09
-!- frispete_(~frispete@p54A90E17.dip0.t-ipconnect.de) has joined #tryton05:19
-!- miknotauro(~miknotaur@187.207.59.241) has joined #tryton06:33
-!- frispete(~frispete@p54A90E17.dip0.t-ipconnect.de) has joined #tryton06:58
-!- zodman_(~zodman@178.62.7.89) has joined #tryton07:01
-!- cedk(~ced@gentoo/developer/cedk) has joined #tryton09:12
-!- aasnan(~angel@48.red-83-45-194.dynamicip.rima-tde.net) has joined #tryton09:17
-!- yangoon_rm(~mathiasb@137.158.22.107) has joined #tryton09:30
-!- Telesight(~anthony@4dae0c97.ftth.telfortglasvezel.nl) has joined #tryton09:33
sisalpHello, following discussion here about trytond-cron, here is the solution I adopted :10:27
sisalpdatabases which need to "croned" have a specific convention on their name (typically the first letters)10:28
sisalplist of databases to be croned is re-evaluated when the service is started10:28
sisalpfor 4.0, a trytond-cron is started for each database10:29
sisalpfor 4.2, a single trytond-cron will start with a list of databases10:29
-!- udono(~udono@ip-37-201-245-214.hsi13.unitymediagroup.de) has joined #tryton10:30
sisalpthis is not comprehensive, some cases are not resolved automatically and after manipulations on databases, you may have to restart the service10:31
sisalpto re-align the trytond-cron database list.10:31
-!- rpit(~rpit@2a02:908:e672:9420:56ee:75ff:fe0d:d3c7) has joined #tryton11:08
cedksisalp: why different solution for 4.0 and 4.2 ?11:20
cedksisalp: I think all databases should have a cron by default11:30
-!- sharkcz(~sharkcz@server.danny.cz) has joined #tryton11:44
-!- shrox(shrox@nat/iiit/x-cooejmiyhvesytan) has joined #tryton12:24
sisalpcedk: 4.0 and 4.2 : because a user can drop a database at anytime from the client and it would block cron for all databases. On 4.2, cron restart will be synchronised with create/drop db.13:05
sisalpI think only production databases should have a cron. test, restored, training should not imho.13:07
-!- Telesight(~anthony@4dae0c97.ftth.telfortglasvezel.nl) has joined #tryton13:09
-!- Timitos(~kpreisler@host-88-217-184-172.customer.m-online.net) has joined #tryton13:26
-!- yangoon_rm(~mathiasb@137.158.22.107) has joined #tryton16:12
-!- yangoon_rm1(~mathiasb@137.158.22.107) has joined #tryton16:21
-!- kstenger(~karla@r186-50-63-234.dialup.adsl.anteldata.net.uy) has joined #tryton16:55
-!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton16:56
-!- yangoon_rm(~mathiasb@137.158.22.107) has joined #tryton17:39
-!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton17:49
-!- rpit(~rpit@2a02:908:e672:9420:56ee:75ff:fe0d:d3c7) has joined #tryton18:42
-!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton20:12
-!- yangoon_rm(~mathiasb@137.158.22.107) has joined #tryton20:21
-!- kstenger1(~karla@r186-50-7-37.dialup.adsl.anteldata.net.uy) has joined #tryton20:40
-!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton21:53

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!