Bug#835104: Bug#864297: unblock: schroot/1.6.10-4
On 2017-06-19 15:08, Raphael Hertzog wrote: > [ Putting Aurélion in copy since he's the one who requested this service > file ] > > On Sun, 18 Jun 2017, Michael Biebl wrote: > > Am 17.06.2017 um 22:27 schrieb Michael Biebl: > > > > > For that create a file > > > /lib/systemd/system/schroot.service.d/timeout.conf (feel free to choose > > > a better name), containing: > > > > > > [Service] > > > Type=oneshot > > > TimeoutSec=infinity > > > > If you only need to change the timeout, I probably wouldn't change Type= > > at all, but only set TimeoutSec= via a drop-in. > > The default is 5min for SysV init scripts. > > I'm surprised that #835104 says that the init scripts are killed after > > 90sec though. > > Can schroot take longer then 5min to start or stop? Do we really need to > > disable the timeout completely (infinity) or would simply increasing the > > value to say 15min be sufficient? > > Aurélien, can you answer Michael's question ? DSA uses this init script with SESSIONS_RECOVER="end" in /etc/default/schroot. When there are dozen of chroots opened (which is common on the porterboxes), the current script takes more than 5 minutes to cleanup all the chroots upon reboot. I guess increasing the timeout is fine, 15min would already be a good start. Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://www.aurel32.net
Bug#835104: Bug#864297: unblock: schroot/1.6.10-4
[ Putting Aurélion in copy since he's the one who requested this service file ] On Sun, 18 Jun 2017, Michael Biebl wrote: > Am 17.06.2017 um 22:27 schrieb Michael Biebl: > > > For that create a file > > /lib/systemd/system/schroot.service.d/timeout.conf (feel free to choose > > a better name), containing: > > > > [Service] > > Type=oneshot > > TimeoutSec=infinity > > If you only need to change the timeout, I probably wouldn't change Type= > at all, but only set TimeoutSec= via a drop-in. > The default is 5min for SysV init scripts. > I'm surprised that #835104 says that the init scripts are killed after > 90sec though. > Can schroot take longer then 5min to start or stop? Do we really need to > disable the timeout completely (infinity) or would simply increasing the > value to say 15min be sufficient? Aurélien, can you answer Michael's question ? Cheers, -- Raphaël Hertzog ◈ Debian Developer Support Debian LTS: https://www.freexian.com/services/debian-lts.html Learn to master Debian: https://debian-handbook.info/get/
Bug#835104: Bug#864297: unblock: schroot/1.6.10-4
Am 17.06.2017 um 22:27 schrieb Michael Biebl: > For that create a file > /lib/systemd/system/schroot.service.d/timeout.conf (feel free to choose > a better name), containing: > > [Service] > Type=oneshot > TimeoutSec=infinity If you only need to change the timeout, I probably wouldn't change Type= at all, but only set TimeoutSec= via a drop-in. The default is 5min for SysV init scripts. I'm surprised that #835104 says that the init scripts are killed after 90sec though. Can schroot take longer then 5min to start or stop? Do we really need to disable the timeout completely (infinity) or would simply increasing the value to say 15min be sufficient? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
