Comment 3 for bug 1072641

Revision history for this message
Michael Lustfield (michaellustfield) wrote : Re: [Bug 1072641] Re: Init scripts on lucid have a pid file in /run which doesn't exist

Are you using the latest PPA? Did you maybe make some modifications to
the init script before upgrading which prevented the new script from
being installed?

On Tue, Oct 30, 2012 at 9:05 AM, Rowan <email address hidden> wrote:
> It's still broken since the pid file never gets put in /run the pid file is set to
> pid /var/run/nginx.pid
>
> You could either update nginx.conf to use /run/nginx.pid or symlink /run
> to /var/run/ in lucid.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1072641
>
> Title:
> Init scripts on lucid have a pid file in /run which doesn't exist
>
> Status in Nginx:
> Fix Released
>
> Bug description:
> In nginx 1.2.4 from https://launchpad.net/~nginx/+archive/stable/ the
> lucid build is attempting to use the pid file in /run
>
>
> 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.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nginx/+bug/1072641/+subscriptions