I enabled remote logging for my home subnet, and syslogd doesn't seem(!) to
be logging the messages.
They ARE making it to the system.
Can someone look at bin/162135 which has all the details, including
tcpdump to show that the messages are making it to the system.
Thanks!
--
Larry Rosenman
On Fri, Oct 28, 2011 at 7:22 PM, Larry Rosenman l...@lerctr.org wrote:
I enabled remote logging for my home subnet, and syslogd doesn't seem(!) to
be logging the messages.
They ARE making it to the system.
Can someone look at bin/162135 which has all the details, including
tcpdump to show
On Fri, 28 Oct 2011, Kevin Oberman wrote:
On Fri, Oct 28, 2011 at 7:22 PM, Larry Rosenman l...@lerctr.org wrote:
I enabled remote logging for my home subnet, and syslogd doesn't seem(!) to
be logging the messages.
They ARE making it to the system.
Can someone look at bin/162135 which has
On Fri, Oct 28, 2011 at 8:37 PM, Larry Rosenman l...@lerctr.org wrote:
On Fri, 28 Oct 2011, Kevin Oberman wrote:
On Fri, Oct 28, 2011 at 7:22 PM, Larry Rosenman l...@lerctr.org wrote:
I enabled remote logging for my home subnet, and syslogd doesn't seem(!)
to
be logging the messages.
They
On Fri, 28 Oct 2011, Kevin Oberman wrote:
OK. I'm baffled! I can't see anything that looks wrong, but I'll think
about it a bit more.
See my reply to Stas (cc'd to you). The issue is the damn
cable modem is sending the packets from random source PORTS, so
the -a entry needed a :* after
