Re: Logger messages getting stuck in a buffer somewhere?

From: Karen Wieprecht (karen.wieprecht_at_jhuapl.edu)
Date: 01/26/05 

Date: Wed, 26 Jan 2005 08:56:17 -0500

Actually, I found something about that yesterday, but setlogsock didn't
recognize "stream" as a valid socket type even though it appears that this
support was added many versions prior to the ones I've been testing.
Someone Suggested I look to see if syslog is blocking networked syslog
messages with "-t". I'll have to check that out. I'll keep you all
posted ...

Karen

"Mike Delaney" <mdelan@computer.org> wrote in message
news:slrncvdui8.5lv.mdelan@angua.ankh.lusars.net...
> On Tue, 25 Jan 2005 09:31:52 -0500 in <ct5l8r$9dl$1@aplcore.jhuapl.edu>,
> Karen Wieprecht said something similar to:
> :
> : I don't think it's a problem with syslogd directly, I've been able to
log
> : one liners with no problem. they show up right away. Also, I've
been
> [snip]
> : Here is a code snippit of what I was testing with perl 5.6.1 (and yes,
> : syslog.conf is configured correctly, logger -p local5.notice "test
message"
> : comes into the system log just fine):
> : ------------------------------------------------------------
> :
> : use Sys::Syslog qw(:DEFAULT setlogsock);
> : setlogsock ("unix");
> : openlog ("audit", "ndelay,nowait", "local5");
>
> Read the Sys::Syslog documentation. On IRIX, you need to use a stream,
not
> a unix domain socket.
>