[Bug 1314740] Re: init script pid parsing has failure cases

2015-07-25 Thread Thomas Ward
This was hit by someone today in the nginx support chat room on Freenode. I found that diff in Debian to fix this, and will likely poke at this today. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu.

[Bug 1314740] Re: init script pid parsing has failure cases

2015-07-25 Thread Thomas Ward
This was fixed in later releases after Trusty. ** Changed in: nginx (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1314740 Title: init

[Bug 1314740] Re: init script pid parsing has failure cases

2015-07-25 Thread Thomas Ward
Additional changes were made in my testing to verbosify the init scripts. I can CONFIRM that this does happen, and will get this in the SRU format. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu.

[Bug 1314740] Re: init script pid parsing has failure cases

2015-07-25 Thread Thomas Ward
This is the diff on this which Debian uses, and we'll likely use that here: http://anonscm.debian.org/cgit/collab-maint/nginx.git/commit/debian /nginx-common.nginx.init?id=b4d1fd4a4ed56f487776adefcc843a031b2a7fbd ** Also affects: nginx (Ubuntu Trusty) Importance: Undecided Status: New

[Bug 1314740] Re: init script pid parsing has failure cases

2015-07-25 Thread Thomas Ward
** Description changed: + [Impact] + + * The init script fails to start correctly due to the parsing used by + the init file. The init file here now will scan all of nginx.conf and + find references to 'pid, rather than the actual pidfile line. + + * This means that other directives can cause

[Bug 1314740] Re: init script pid parsing has failure cases

2014-09-04 Thread Bug Watch Updater
** Changed in: nginx (Debian) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1314740 Title: init script pid parsing has failure cases To

[Bug 1314740] Re: init script pid parsing has failure cases

2014-08-28 Thread Bug Watch Updater
** Changed in: nginx (Debian) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1314740 Title: init script pid parsing has failure cases To manage

[Bug 1314740] Re: init script pid parsing has failure cases

2014-06-04 Thread Greg Lutostanski
PID=$(sed -n 's/^\s*pid\s\s*\([^;]*\).*/\1/p' /etc/nginx/nginx.conf) works for the three testcases shown in this and linked bugs. not sure why I cant use \s+ after pid in the expression above, but it works this way. ** Bug watch added: Debian Bug tracker #747329

[Bug 1314740] Re: init script pid parsing has failure cases

2014-06-04 Thread Bug Watch Updater
** Changed in: nginx (Debian) Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu. https://bugs.launchpad.net/bugs/1314740 Title: init script pid parsing has failure cases To manage

[Bug 1314740] Re: init script pid parsing has failure cases

2014-06-03 Thread Robie Basak
** Summary changed: - awk in startup script finds wrong pid + init script pid parsing has failure cases ** Tags added: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nginx in Ubuntu.