On Wednesday 02 December 2009, Adrian von Bidder wrote: > I tried the patch below and adding qcontrol as rcS.d/S00qcontrol, but > apparently I made some mistake (or is /var/run not accessible yet?)
A solution would have to allow for /var or /var/run to be on a separate file system, so with the current version of qcontrol that would mean the earliest possible point is after local filesystems have been mounted. However, a new upstream version of qcontrol is being worked on [1] introduces a "--direct" mode which does not use the socket file. With that option qcontrol can be run at any time that the command itself and the config file is available. There's a few things missing in the new upstream version and work on it is currently stalled, so I'm unsure when it could be uploaded. I'm also not sure that I want to add an additional early init script by default as different users might have different wishes as to when extra signalling should be done, e.g: - when initrd is loaded (i.e: include qcontrol in the initrd); - when root FS is mounted in initrd; - immediately after init is started (your suggestion); - after local file systems are mounted; - after sshd is started; - ... My feeling is that it should just be documented how it can be done and then left to the user. [1] It also has a proper daemon mode. Experimental version is available in "svn" branches in http://git.debian.org/?p=collab-maint/qcontrol.git. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
