1518918927 Q * Ghislain Quit: Leaving.
1518933457 Q * _are_ Ping timeout: 480 seconds
1518934019 J * _are_ ~quassel@2a01:238:4325:ca00:f065:c93c:f967:9285
1518945031 N * Bertl_zZ Bertl
1518945036 M * Bertl  morning folks!
1518952992 M * Bertl  off to now ... bbl
1518952994 N * Bertl Bertl_oO
1518956511 Q * Aiken Remote host closed the connection
1518972798 J * Ghislain ~ghislain@81.56.195.31
1518984475 J * Aiken ~Aiken@2001:44b8:2168:1000:b26e:bfff:fe2a:b951
1518992544 M * Le_Coyote Bertl_oO: hi :) Is there a chance the vserver initscript now starts vservers in parallel instead of in a sequence? I'm using iptables in a pre-start script, and it tends to lock now using 4.x while I never had the problem with 3.18 AFAICT
1518992599 M * Le_Coyote I ended up adding -w to iptables everywhere, and that solved the problem, but I couldn't find much in the docs/faq about the start sequence. Cheers :)
1518992719 M * Le_Coyote Dunno why that would be kernel-related though
1518992914 M * Bertl_oO it isn't and yes since a while ago (some years?) util-vserver does parallel startup
1518992952 M * Bertl_oO but you can have dependencies or force sequential startup
1518993172 M * Le_Coyote Oh ok, I must've missed that. How is that configured? Or where is the doc for it?
1518993276 M * Le_Coyote Couldn't find it on the flower page nor in the faq
1518993826 M * Le_Coyote I guess since now the pre-start script has to wait for the other to release the iptables lock, it doesn't matter much, but I'd still like to know
1518994187 M * Le_Coyote 'nite