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. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683 E-Mail: l...@lerctr.org US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 _______________________________________________ freebsd-bugs@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
Since Doug Barton doesn't believe that the syslogd is running with the
options, here's a ps to show that it is:
- bin/162135: remote syslog not logging Larry Rosenman
- Re: bin/162135: remote syslog not logging dougb
- Re: bin/162135: remote syslog not logging Larry Rosenman
- Re: bin/162135: remote syslog not logging Remko Lodder
- Re: bin/162135: remote syslog not logging Larry Rosenman
- Re: bin/162135: remote syslog not logging Remko Lodder