So something IS sending it twice, once at pri 22, no flags, then once
at 166 flags 17. (Unless by some configuration flukeyness its reprocessing
the line). So IMHO its not getting something improperly terminated. Its
getting the line twice at different pri/flags causing it to prepend
On Oct 16, 2007, at 6:01 PM, Matt Emmerton wrote:
There must be somewhere in the kernel where we're writing to the
syslog with an empty error string. The syslog routines expect a
newline-terminated character string, so the lack of a newline
causes the next entry to be on the same line as
On Oct 16, 2007, at 6:01 PM, Matt Emmerton wrote:
There must be somewhere in the kernel where we're writing to the
syslog with an empty error string. The syslog routines expect a
newline-terminated character string, so the lack of a newline
causes the next entry to be on the same
I understand there isn't a problem with the first one, but then its
logging
the second as a kernel: entry. My syslog.conf is :
*.err;kern.debug;auth.notice;mail.crit /dev/console
*.emerg *
*.debug
- Original Message -
From: Tuc at T-B-O-H.NET [EMAIL PROTECTED]
To: freebsd-questions@freebsd.org
Sent: Tuesday, October 16, 2007 8:05 PM
Subject: syslog marking sendmail output as kernel:
Hi,
I'm seeing in the logs :
Oct 16 00:00:25 valhalla sm-mta[69206]: l9G40Kf5069206:
It's just a formatting issue.
Oct 16 00:00:25 valhalla sm-mta[69206]: l9G40Kf5069206: SYSERR(root):
snip
Oct 16 00:00:25 valhalla kernel: added newline
Oct 16 00:00:25 valhalla sm-mta[69206]: l9G40Kf5069206: SYSERR(root):
snip
There must be somewhere in the kernel where
I understand there isn't a problem with the first one, but then its
logging
the second as a kernel: entry. My syslog.conf is :
*.err;kern.debug;auth.notice;mail.crit /dev/console
*.emerg *
*.debug
