Bug 11230

Summary:	daemontools svscan should start via inittab, not init script
Product:	Gentoo Linux	Reporter:	Jeremy Wohl <jeremyw-gentoo-bugzilla1>
Component:	Current packages	Assignee:	SpanKY <vapier>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	sascha-gentoo-bugzilla
Priority:	Normal
Version:	1.4_rc1
Hardware:	x86
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Jeremy Wohl 2002-11-25 19:27:34 UTC

I posit that starting svscan by init script, and not DJB's suggested inittab 
method, is dangerous.

Example: new to the Gentoo system, I've tripped on a few changes to outlying 
network interface confs (i.e. not primary & therefore not critical) that 
caused the 'net' init dependency to fail.  Thus, on next boot, failing to run 
svscan.  Thus failing to start critical services, like ssh.  Thus making a 
remote box dead in the water.

Svscan should always be given a chance to run.

(Of course, this also protects from svscan failure -- init will restart it.)

Comment 1 Daniel Robbins (RETIRED) gentoo-dev

2003-09-09 15:38:47 UTC

Mike, can you make this an option and add some postinst() info about how to do it? init monitors for dead processes and then will respawn them, which is why DJB uses it. currently, gentoo initscripts do not do this.

Comment 2 SpanKY gentoo-dev

2003-09-09 20:55:24 UTC


*** This bug has been marked as a duplicate of 28294 ***