Date: Tue, 13 Nov 2001 01:29:06 -0800 From: "Crist J. Clark" <cristjc@earthlink.net> To: Jean-Yves Lefort <jylefort@brutele.be> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: syslogd stopping reporting to a remote host after that host has been down Message-ID: <20011113012906.H45158@blossom.cjclark.org> In-Reply-To: <20011111161936.A6625@jsite.lefort.net>; from jylefort@brutele.be on Sun, Nov 11, 2001 at 04:19:36PM %2B0100 References: <20011111161936.A6625@jsite.lefort.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 11, 2001 at 04:19:36PM +0100, Jean-Yves Lefort wrote:
> Hi all.
>
> A few days ago i finally moved my family internet gateway from my own
> workstation to a dedicated server. On that server i have configured
> syslogd to dup the logs to my workstation, so that i can see what's happening
> without having to ssh to the gateway.
> The thing works absolutely fine but there is something annoying:
> Whenever i shutdown my workstation, the gateway stops logging to my workstation;
> this is normal, but when i bring my workstation up again, the gateway's syslogd
> dont seems to notice it and i have to ssh to that gateway and do a
> 'killall -HUP syslogd' in order to reactivate the remote logging.
This is known behavior. See PR bin/31029.
--
Crist J. Clark | cjclark@alum.mit.edu
| cjclark@jhu.edu
http://people.freebsd.org/~cjc/ | cjc@freebsd.org
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?20011113012906.H45158>