-g command line broken in Nginx 1.2.0

Server NGINX
1

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi.

It seems a change in configuration parsing done in Nginx 1.2.0 [1],
broke the -g option.

$nginx -p . -c conf/nginx.conf -t -g daemon=off
nginx: [emerg] unexpected end of parameter, expecting “;” in command
line
nginx: configuration file ./conf/nginx.conf test failed

[1] nginx-vendor-current: f41d4b305d22

Thanks Manlio
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+mKOEACgkQscQJ24LbaUQI3ACeJrAKNIq5MMcJ9U5Us1z2Rglg
nvgAnjx3zVwbAQEBsX7v0Zaj0UAmHUiv
=bWF9
-----END PGP SIGNATURE-----

2

Hi,

It seems a change in configuration parsing done in Nginx 1.2.0 [1],
broke the -g option.

$nginx -p . -c conf/nginx.conf -t -g daemon=off
nginx: [emerg] unexpected end of parameter, expecting “;” in command line
nginx: configuration file ./conf/nginx.conf test failed

I’m not sure where did you come up with that syntax, but it’s wrong.

man nginx

Best regards,
Piotr S. < [email protected] >

3

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Il 06/05/2012 09:48, Piotr S. ha scritto:

Thanks.

I don’t remember why I started to use that syntax.

Manlio P.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+mMvUACgkQscQJ24LbaURDdACfSnNyTAoWzDSaxzyQhPZ3yhZB
sz0AoIvrww3PJiv26eBKULyBcIyn/4Hi
=gAH2
-----END PGP SIGNATURE-----