bin/162135: remote syslog not logging

[Remko Lodder]

So it wasnt a problem in the code..
I think we can safely say that Doug was right..

Cheers

Sent from my iPad

On Oct 29, 2011, at 10:26 AM, Larry Rosenman <ler at lerctr.org> wrote:

> We found the issue, I needed to add a :* to the end of the -a option addresses since the Cable modem is using anonymous ports for the source instead of 514. I'm now getting the messages.
> -- 
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.
> 
> Remko Lodder <remko at elvandar.org> wrote:
> 
> 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 at elvandar.org
> \ /   Remko Lodder			| remko at FreeBSD.org
> X    FreeBSD					| http://www.evilcoder.org
> / \   The Power to Serve		| Quis custodiet ipsos custodes
>