Package: schroot Version: 1.6.10-2 Severity: normal Dear Maintainer,
schroot provides an initscript which can take quite some time to execute, for example if configured to end up all active sessions. When running under systemd, it is often killed after the default 90 seconds timeout. This happens regularly on the Debian porterboxes where many users leave their chroot sessions opened. The solution is probably to provide a systemd service file running in oneshot mode, so that it defaults to no timeout. Thanks, Aurelien -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.6.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
