Date: Sat, 29 Oct 2011 07:29:49 +0200 From: Remko Lodder <remko@elvandar.org> To: Larry Rosenman <ler@lerctr.org> Cc: freebsd-bugs@FreeBSD.org, Doug Barton <dougb@FreeBSD.org> Subject: Re: bin/162135: remote syslog not logging Message-ID: <E862A153-5D12-42E0-AD46-F2C2639E41C0@elvandar.org> In-Reply-To: <alpine.BSF.2.00.1110282157310.70260@borg> References: <201110290220.p9T2K6tf076178@freefall.freebsd.org> <alpine.BSF.2.00.1110282157310.70260@borg>
next in thread | previous in thread | raw e-mail | index | archive | help
On Oct 29, 2011, at 4:59 AM, Larry Rosenman wrote: > Since Doug Barton doesn't believe that the syslogd is running with the options, here's a ps to show that it is: > > > root 65128 0.0 0.0 12216 1552 ?? Ss 10:02AM 0:01.17 /usr/sbin/syslogd -n -a 192.168.200.10 -a 192.168.200.0/24 > ler 70268 0.0 0.0 14680 1608 0 S+ 9:58PM 0:00.00 sh -c ps auxw|grep syslogd > ler 70270 0.0 0.0 16460 1352 0 S+ 9:58PM 0:00.00 grep syslogd > > And in answer to Doug's point that the -a options are redundant, I know that > but I did it as a debugging set. > > I think this proves that there is a PROBLEM in the code, and the PR should > be reopened. > > I object STRONGLY to the closure of this PR. > > I doubt this is a PROBLEM in the code. I have syslog running for many many networks and they are not local (remote logging); Please investigate this first and ask around before submitting a PR. I strongly suggest to NOT reopen the PR at this point. Cheers Remko HAT: Bugmeister -- /"\ With kind regards, | remko@elvandar.org \ / Remko Lodder | remko@FreeBSD.org X FreeBSD | http://www.evilcoder.org / \ The Power to Serve | Quis custodiet ipsos custodes
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E862A153-5D12-42E0-AD46-F2C2639E41C0>