runsvdir does not use upstart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
git-core (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
runit (Ubuntu) |
Fix Released
|
Medium
|
Luca Falavigna |
Bug Description
runsvdir does not use upstart. This causes the following two issues:
Doesn't start after being installed:
After installing 'runit' and 'socklog' in order to use 'bincimap', my system fails to run 'runsvdir' at boot-up. This is despite the fact that '/etc/inittab' has been rewritten to contain the stanza:
#-- runit begin
SV:123456:
#-- runit end
Searching for messages in the system logs turns up nothing
ferrix:~# find /var/log -type f -exec grep -l -e 'runit\|runsvdir' {} \;
/var/log/auth.log
/var/log/dpkg.log.1
/var/log/
/var/log/
/var/log/auth.log.0
Searching for the process
ferrix:~# ps ax | grep runsvdir
also reveals nothing
However, executing 'runsvdir-start' by hand brings the subsystem up without error
Cannot be installed:
cp: cannot stat `/etc/inittab': No such file or directory
dpkg: error processing runit (--configure):
subprocess post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of ebox:
ebox depends on runit; however:
Package runit is not configured yet.
dpkg: error processing ebox (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
runit
ebox
E: Sub-process /usr/bin/dpkg returned an error code (1)
Related branches
Changed in runit: | |
importance: | Undecided → Medium |
Changed in runit: | |
assignee: | nobody → dktrkranz |
Changed in git-core: | |
status: | New → Invalid |
I'm seeing this too. Presumably this is because the runit package doesn't handle being installed alongside upstart yet.
For now, I've just added the following to /etc/event. d/runsvdir:
start on startup
stop on shutdown
respawn /usr/sbin/ runsvdir- start