That is my best guess at this point.
On Jul 27, 2005, at 4:31 AM, Kai Schaetzl wrote:
Steve Martin wrote on Tue, 26 Jul 2005 19:31:07 -0500:
(MacOS
X 10.4.2).
could it be something specific to the Mac or this Syslog version on
this
OS X version?
Kai
--
Kai Schätzl, Berlin, Germany
Ge
Steve Martin wrote on Tue, 26 Jul 2005 19:31:07 -0500:
> (MacOS
> X 10.4.2).
could it be something specific to the Mac or this Syslog version on this
OS X version?
Kai
--
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com
IE-Center: http://ie5.
From: "Loren Wilton" <[EMAIL PROTECTED]>
> > I was curious why spamd log entries always had an extra blank line
> > after them.
> >
> > It looks like Sys::Syslog always does that so any perl script
> > reporting to syslog via that mechanism has extra blank lines. (MacOS
> > X 10.4.2).
>
> I would
That is what I thought, but I test with a simple perl script to call
syslog with a string with no terminating new line and it does indeed
add two. I also looked at the spamd code that calls syslog and it
strips off any trailing newlines.
I guess it is just built into Sys::Syslog.
On Jul 2
> I was curious why spamd log entries always had an extra blank line
> after them.
>
> It looks like Sys::Syslog always does that so any perl script
> reporting to syslog via that mechanism has extra blank lines. (MacOS
> X 10.4.2).
I would guess, without looking at any code, that the syslog stuf
I was curious why spamd log entries always had an extra blank line
after them.
It looks like Sys::Syslog always does that so any perl script
reporting to syslog via that mechanism has extra blank lines. (MacOS
X 10.4.2).
Anyone know why or if there is a way to change that behavior?
--
Steve Ma
