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

chat.freenode.net #tryton log beginning Sat Jul 2 00:00:01 CEST 2016
2016-07-02 01:01 -!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton
2016-07-02 01:44 -!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton
2016-07-02 02:09 -!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton
2016-07-02 05:19 -!- frispete_(~frispete@p54A90E17.dip0.t-ipconnect.de) has joined #tryton
2016-07-02 06:33 -!- miknotauro(~miknotaur@187.207.59.241) has joined #tryton
2016-07-02 06:58 -!- frispete(~frispete@p54A90E17.dip0.t-ipconnect.de) has joined #tryton
2016-07-02 07:01 -!- zodman_(~zodman@178.62.7.89) has joined #tryton
2016-07-02 09:12 -!- cedk(~ced@gentoo/developer/cedk) has joined #tryton
2016-07-02 09:17 -!- aasnan(~angel@48.red-83-45-194.dynamicip.rima-tde.net) has joined #tryton
2016-07-02 09:30 -!- yangoon_rm(~mathiasb@137.158.22.107) has joined #tryton
2016-07-02 09:33 -!- Telesight(~anthony@4dae0c97.ftth.telfortglasvezel.nl) has joined #tryton
2016-07-02 10:27 <sisalp> Hello, following discussion here about trytond-cron, here is the solution I adopted :
2016-07-02 10:28 <sisalp> databases which need to "croned" have a specific convention on their name (typically the first letters)
2016-07-02 10:28 <sisalp> list of databases to be croned is re-evaluated when the service is started
2016-07-02 10:29 <sisalp> for 4.0, a trytond-cron is started for each database
2016-07-02 10:29 <sisalp> for 4.2, a single trytond-cron will start with a list of databases
2016-07-02 10:30 -!- udono(~udono@ip-37-201-245-214.hsi13.unitymediagroup.de) has joined #tryton
2016-07-02 10:31 <sisalp> this is not comprehensive, some cases are not resolved automatically and after manipulations on databases, you may have to restart the service
2016-07-02 10:31 <sisalp> to re-align the trytond-cron database list.
2016-07-02 11:08 -!- rpit(~rpit@2a02:908:e672:9420:56ee:75ff:fe0d:d3c7) has joined #tryton
2016-07-02 11:20 <cedk> sisalp: why different solution for 4.0 and 4.2 ?
2016-07-02 11:30 <cedk> sisalp: I think all databases should have a cron by default
2016-07-02 11:44 -!- sharkcz(~sharkcz@server.danny.cz) has joined #tryton
2016-07-02 12:24 -!- shrox(shrox@nat/iiit/x-cooejmiyhvesytan) has joined #tryton
2016-07-02 13:05 <sisalp> cedk: 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.
2016-07-02 13:07 <sisalp> I think only production databases should have a cron. test, restored, training should not imho.
2016-07-02 13:09 -!- Telesight(~anthony@4dae0c97.ftth.telfortglasvezel.nl) has joined #tryton
2016-07-02 13:26 -!- Timitos(~kpreisler@host-88-217-184-172.customer.m-online.net) has joined #tryton
2016-07-02 16:12 -!- yangoon_rm(~mathiasb@137.158.22.107) has joined #tryton
2016-07-02 16:21 -!- yangoon_rm1(~mathiasb@137.158.22.107) has joined #tryton
2016-07-02 16:55 -!- kstenger(~karla@r186-50-63-234.dialup.adsl.anteldata.net.uy) has joined #tryton
2016-07-02 16:56 -!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton
2016-07-02 17:39 -!- yangoon_rm(~mathiasb@137.158.22.107) has joined #tryton
2016-07-02 17:49 -!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton
2016-07-02 18:42 -!- rpit(~rpit@2a02:908:e672:9420:56ee:75ff:fe0d:d3c7) has joined #tryton
2016-07-02 20:12 -!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton
2016-07-02 20:21 -!- yangoon_rm(~mathiasb@137.158.22.107) has joined #tryton
2016-07-02 20:40 -!- kstenger1(~karla@r186-50-7-37.dialup.adsl.anteldata.net.uy) has joined #tryton
2016-07-02 21:53 -!- JosDzG(~Thunderbi@fixed-203-141-189-203-141-123.iusacell.net) has joined #tryton

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!