Date: Thu, 7 Mar 2002 16:27:13 -0600 From: "Mike Meyer" <mwm-dated-1015972034.78f9e0@mired.org> To: "Martin Gignac" <freebsd@mobilitylab.net> Cc: "Mike Meyer" <mwm-dated-1015921013.0775c3@mired.org>, freebsd-questions@freebsd.org Subject: Re: Weird syslogd behavior when logging to remote hosts? Message-ID: <15495.59713.840372.942946@guru.mired.org> In-Reply-To: <20020307084329.M53558@mobilitylab.net> References: <59442089@toto.iv> <15495.8693.313723.431169@guru.mired.org> <20020307084329.M53558@mobilitylab.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Martin Gignac <freebsd@mobilitylab.net> types: > I did find a PR concerning this behavior when the server stops responding, > but in my case, it is after I reboot the _client_ that it seems to stop > sending its logs (I wrongly used the term 'server' in my previous e-mail--I > was actually talking about the client). I need to perform the 'killall -HUP > syslogd' on the client before it will begin sending logging information to > the syslog server. Have you heard of _this_ particular behavior? Nope, that I haven't seen nor heard of. > As for daemontools, I already use it. I know it comes with multilog. Are you > suggesting I use it for remote logging? I didn't think it could that. Is > there a way to consolidate all logs on a single host by using multilog in a > certain configuration? I've done that twice now. I could swear djb wrote tools to do remote logging safely. Maybe it's in the ucsd-tcpi port? <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?15495.59713.840372.942946>