ngircd refuses to start automatically through sysv init
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ngircd (Ubuntu) |
Fix Released
|
Medium
|
Adrien Cunin | ||
Hardy |
Fix Released
|
Medium
|
Adrien Cunin |
Bug Description
Binary package hint: ngircd
Reason seems to be that the init script uses /var/run/
Note that directly after installation the daemon started correctly, just not after a reboot.
Proposed fix: use /var/run/ngircd.pid as pidfile, as a lot of other daemons do.
-- SRU for hardy
This bug makes the daemon fail to start after each reboot of the computer, because the init script doesn't create /var/run/ngircd/ and /var/run/ is a tmpfs in Ubuntu. The fix is pretty safe, it's a one-liner creating that directory with mkdir -p. It is exactly the same as the one in intrepid.
TEST CASE: install ngircd, reboot your computer, see it fails to start. install the -proposed ngircd, reboot your computer, see it starts successfully.
Changed in ngircd: | |
status: | New → Confirmed |
Changed in ngircd: | |
assignee: | nobody → adri2000 |
Changed in ngircd: | |
importance: | Undecided → Medium |
status: | Confirmed → In Progress |
assignee: | nobody → adri2000 |
importance: | Undecided → Medium |
status: | New → In Progress |
description: | updated |
Changed in ngircd: | |
status: | In Progress → Fix Committed |
Changed in ngircd: | |
status: | Fix Committed → Fix Released |
Still seeing this as of the gutsy upgrade. Alternate workaround is this in /etc/rc.local:
# ngircd lock directory workaround
mkdir /var/run/ngircd/
and then making sure rc.local runs at priority 11.
This bug was seen with both mrtg and smokeping. I believe their final fixes were to do detection of the lockfile directory as part of the initscript and create it if it did not exist.