On Fri, Jan 17, 2014 at 12:05:22PM +0100, Holger Levsen wrote:
Hi,
On Donnerstag, 16. Januar 2014, Anthony Towns wrote:
it's not realistic for a porter to continously test startup
scripts for thousands of packages.
It's reasonable to semi-continuously test installation scripts for
thousands of packages -- that's what piuparts does, and we have
sponsored cloud resources to support that. It seems like that would be
fairly straightforward to duplicate for testing packages with
alternative init systems.
piuparts has /sbin/policy.rc.d in place with the content of exit 0, IOW, it
does not execute init scripts at all. Running, monitoring and killing
arbitrary daemons is not trivial.
Indeed. Early on in my original development of piuparts I realised
that testing, in a chroot, code that starts arbitrary daemons is a bad
idea in oh so many ways. I haven't followed piuparts development in
recent years, so I don't know if it still uses chroot, but unless it's
started using containers or virtual machines, it should continue to
NOT allow init.d scripts to run. At all.
--
http://www.cafepress.com/trunktees -- geeky funny T-shirts
http://gtdfh.branchable.com/ -- GTD for hackers
--
To UNSUBSCRIBE, email to debian-ctte-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140117111506.gd5...@mavolio.codethink.co.uk
