Yes, of course but I like none of these propositions. I would like loghost stays independent of network updates (update of IP, subnet...). Is it not possible when a destination is unreachable (or unreadable, or ...) that syslog-ng logs an error in syslog.crit (if possible ;-)), continues its job and retries to open failed destination at next message. Thanks for your help and your indulgence. On Fri, Apr 26, 2002 at 03:02:44PM +0200, Balazs Scheidler wrote:
On Fri, Apr 26, 2002 at 02:57:54PM +0200, Jerome Peducasse wrote:
If a computer reboot before DNS server, syslog-ng disallows starting because it can't resolve IP address of loghost. It's akward because computer can't write in local destination.
you should either use IP addresses in your configuration, _or_ add loghost into your /etc/hosts
-- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
_______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng
-- Jerome Peducasse Wanadoo Portails - Sophia Antipolis