/var/run/popfile does not get re-created after reboot
Bug #126894 reported by
Daniel Hahler
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
popfile (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Feisty |
Fix Released
|
Medium
|
Scott Kitterman |
Bug Description
Binary package hint: popfile
After reboot, the popfile log is full of the following entries:
2007/7/19 01:56:36 23039: config: 185: New POPFile instance detected and signalled
2007/7/19 01:56:41 23039: config: 185: New POPFile instance detected and signalled
Additionally, "invoke-rc.d popfile stop" claims that popfile is not running.
The problem is that /var/run/popfile, the default location of the pidfile, does not get created, if it does not exist.
Changed in popfile: | |
assignee: | nobody → kitterman |
status: | Triaged → In Progress |
status: | New → Confirmed |
Changed in popfile: | |
status: | Fix Committed → Fix Released |
Changed in popfile: | |
assignee: | blueyed → kitterman |
status: | Confirmed → In Progress |
To post a comment you must log in.
Please find a fix for this attached.
I'm not providing a debdiff yet, because I'm not sure this is the correct way to fix this.
Basically, it adds the following lines to the beginning of the init script:
mkdir -p `dirname $PIDFILE`
chown -R popfile.popfile `dirname $PIDFILE`