From 21c3ff1daaed28647413cd1fb4ce4fc69f9f592a Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Fri, 17 Nov 2017 19:53:20 -0400 Subject: don't start services in chroots Service: Changed to use invoke-rc.d rather than service for starting services. This notably means that in chroots, services will not be started. This seems like the right thing to do, because running services inside a chroot is problimatic. Use a real container system for running services. Fixes the problem that, when building a disk image, using eg, Apt.servicesInstalledRunning caused the service to be started in the chroot, even though a policy-rc.d was in place to prevent it, because the "service" command does not check policy-rc.d. This commit was sponsored by John Peloquin on Patreon. --- debian/changelog | 3 +++ 1 file changed, 3 insertions(+) (limited to 'debian') diff --git a/debian/changelog b/debian/changelog index 894c906f..75a0df5c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -15,6 +15,9 @@ propellor (4.9.1) UNRELEASED; urgency=medium * Uboot: New module. * Machine: New module, machine-specific properties for ARM boards are being collected here. + * Service: Changed to use invoke-rc.d rather than service for starting + services. This notably means that in chroots, services will not be + started. -- Joey Hess Thu, 02 Nov 2017 10:28:44 -0400 -- cgit v1.3-2-g0d8e