[syslog-ng]odd problem
Balazs Scheidler
bazsi@balabit.hu
Tue, 3 Apr 2001 10:30:12 +0200
On Mon, Apr 02, 2001 at 01:51:27PM -0400, jon@dumbo.pobox.com wrote:
> i noticed yesterday that syslog-ng won't log to anything in a destination() section if
> one of them fails.
>
> we have a remote logging machine colocated somewhere...here is its config(just the useful stuff)
>
> destination macrogenerateddaily {
> tcp(208.210.124.50 port(514));
> file("/var/log/ng/$HOST/$YEAR$MONTH$DAY/$FACILITY.$PRIORITY" dir_per
> m(0755) perm(0644));
> };
>
> destination macrogeneratedhourly {
> tcp(208.210.124.50 port(514));
> file("/var/log/ng/$HOST/$YEAR$MONTH$DAY/$FACILITY.$PRIORITY.$HOUR" d
> ir_perm(0755) perm(0644));
> };
>
>
> now....we lost internet connectivity (so the tcp link failed)
> unfortunately, it also stopped logging to the disk.
> does it log to destinations, then just die as soon as one fails?
no, it shouldn't. destinations are completely independent.
--
Bazsi
PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1