[syslog-ng]SIGHUP: messages logged in the wrong order
José Pedro Oliveira
syslog-ng@lists.balabit.hu
Thu, 02 Sep 2004 21:44:09 +0100
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4E1B170AAFD1F5997BFF20A0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
When syslog-ng receives the SIGHUP signal it logs the following
two messages out of order:
...
Sep 2 21:21:51 pateta syslog-ng[13490]: new configuration initialized
Sep 2 21:21:50 pateta syslog-ng[13490]: SIGHUP received, restarting
syslog-ng
...
Shouldn't the first message have been logged after the one reporting
the reception of the SIGHUP signal (check the timestamps)?
Tested syslog-ng versions:
Syslog-ng 1.6.5 in a Fedora Core 2 system
Syslog-ng 1.6.2 in a Red Hat 7.3 system
Regards,
jpo
--
José Pedro Oliveira
* mailto: jpo@di.uminho.pt * http://gsd.di.uminho.pt/~jpo *
* gpg fingerprint = F9B6 8D87 859D 1C94 48F0 84C0 9749 9EB5 91BD 851B *
--------------enig4E1B170AAFD1F5997BFF20A0
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFBN4Ydl0metZG9hRsRAh2DAJ9aZm1X+yynipH/3vubtMj7Mo62cgCfZead
ZZH5s41UKBj+eZea7CTYzlI=
=Shdj
-----END PGP SIGNATURE-----
--------------enig4E1B170AAFD1F5997BFF20A0--