Init scripts on lucid have a pid file in /run which doesn't exist
Bug #1072641 reported by
Rowan Wookey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Nginx |
Fix Released
|
High
|
Michael Lustfield |
Bug Description
In nginx 1.2.4 from https:/
start() {
test_nginx_config
# Check if the ULIMIT is set in /etc/default/nginx
if [ -n "$ULIMIT" ]; then
# Set the ulimits
ulimit $ULIMIT
fi
start-stop-daemon --start --quiet --pidfile /run/$NAME.pid \
--retry 5 --exec $DAEMON -- $DAEMON_OPTS || true
}
/run doesn't exist on lucid it should be reverted back to /var/run currently this build can't be restarted without killing nginx and the status check fails.
Changed in nginx: | |
status: | New → Incomplete |
status: | Incomplete → In Progress |
assignee: | nobody → Michael Lustfield (michaellustfield) |
importance: | Undecided → High |
To post a comment you must log in.
/run has been added to nginx-common.dirs so whether or not /run is part of the normal file system layout, it will be sure to exist. I can understand that this might break some policies for lucid, but lucid is the only release that currently lacks /run. I don't plan to maintain yet another "special case". Especially not one that I can solve with this simple solution.
This resolution has been uploaded and published in the ppa.