[syslog-ng]1.4.11 fixes SIGHUP problems?

[Hamilton, Andrew Mr RAYTHEON 5 SIG CMD]

I definitely agree that there is nothing more that can be done.  I write my
internal() source to a different file and after I HUP the daemon I just tail
the file and I know whether the config was any good.  You could write a
wrapper script that HUPped the daemon and tailed the output of your internal
file all for you on restart.  That would at least give you immediate
gratification, which is what this is all about anyway, right?

Regards,
Drew

> -----Original Message-----
> From:	Scott McDermott [SMTP:mcdermot@questra.com]
> Sent:	Monday, March 12, 2001 10:10 PM
> To:	syslog-ng@lists.balabit.hu
> Subject:	Re: [syslog-ng]1.4.11 fixes SIGHUP problems?
> 
> Balazs Scheidler on Mon 12/03 19:07 +0100:
> > > Can't you just write it to the internal source ?
> > 
> > I _write_ it there, that's why it pops up in logs.
> 
> Then there's nothing more that can be done :) Person in question will
> just have to maintain a regex watcher on the logs for failures.  Since
> syslog-ng closes all its terminal-inherited FDs, forks and sets SID, I
> don't see where else it would go...I mean you could write it to
> /dev/console but that's icky.
> 
> _______________________________________________
> syslog-ng maillist  -  syslog-ng@lists.balabit.hu
> https://lists.balabit.hu/mailman/listinfo/syslog-ng