conf/62368: 5.2-RELEASE syslog.conf appears to be malformed
Kline, Erik
Erik.Kline at netapp.com
Wed Feb 4 18:10:12 PST 2004
The following reply was made to PR conf/62368; it has been noted by GNATS.
From: "Kline, Erik" <Erik.Kline at netapp.com>
To: "Pat Lashley" <patl+freebsd at volant.org>
Cc: <freebsd-gnats-submit at FreeBSD.org>
Subject: Re: conf/62368: 5.2-RELEASE syslog.conf appears to be malformed
Date: Wed, 4 Feb 2004 18:05:32 -0800
This is a multi-part message in MIME format.
------_=_NextPart_001_01C3EB8C.896BD480
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
so when writing scripts that make custom mods to syslog.conf I need to
cat >> /etc/syslog.conf something like:
!*
local2.info @some.log.host
Is this correct? Thanks for pointing out the section of the man page I
didn't quite get down to!
On Wed, 4 Feb 2004, Pat Lashley wrote:
> --On Wednesday, February 04, 2004 17:24:17 -0800 Erik Kline =
<kline at netapp.com> wrote:
>
> >> Number: 62368
> >> Category: conf
> >> Synopsis: 5.2-RELEASE syslog.conf appears to be malformed
> >
> >> Description:
> > /etc/syslog.conf contains the following lines at the tail end of the =
file:
> >
> > !startslip
> > *.* /var/log/slip.log
> > !ppp
> > *.* /var/log/ppp.log
> >
> > These don't appear to be syntactically valid. Any entries appended
> > after these aren't parsed and processed. CVSup today (04 Feb 2004)
> > shows that /usr/src/etc/syslog.conf remains malformed.
>
> man syslog.conf:
>
> Each block of lines is separated from the previous block by a =
program or
> hostname specification. A block will only log messages =
corresponding to
> the most recent program and hostname specifications given. Thus, =
with a
> block which selects `ppp' as the program, directly followed by a =
block
> that selects messages from the hostname `dialhost', the second =
block will
> only log messages from the ppp(8) program on dialhost.
>
> A program specification is a line beginning with `#!prog' or =
`!prog' (the
> former is for compatibility with the previous syslogd, if one is =
sharing
> syslog.conf files, for example) and the following blocks will be =
associ-
> ated with calls to syslog(3) from that specific program. A =
program spec-
> ification for `foo' will also match any message logged by the =
kernel with
> the prefix `foo: '. The `#!+prog' or `!+prog' specification =
works just
> like the previous one, and the `#!-prog' or `!-prog' =
specification will
> match any message but the ones from that program. A hostname =
specifica-
> tion of the form `#+hostname' or `+hostname' means the following =
blocks
> will be applied to messages received from the specified hostname. =
Alter-
> natively, the hostname specification `#-hostname' or `-hostname' =
causes
> the following blocks to be applied to messages from any host but =
the one
> specified. If the hostname is given as `@', the local hostname =
will be
> used. A program or hostname specification may be reset by giving =
the
> program or hostname as `*'.
>
> The reason that lines added after that point don't appear to be
> parsed or processed is that they apply only to messages from programs
> named 'ppp'.
>
>
>
> -Pat
>
------_=_NextPart_001_01C3EB8C.896BD480
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.0.6249.1">
<TITLE>Re: conf/62368: 5.2-RELEASE syslog.conf appears to be =
malformed</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>
<P><FONT SIZE=3D2>so when writing scripts that make custom mods to =
syslog.conf I need to</FONT>
<BR><FONT SIZE=3D2>cat >> /etc/syslog.conf something like:</FONT>
</P>
<P><FONT SIZE=3D2>!*</FONT>
<BR><FONT SIZE=3D2>local2.info =
@some.log.host</FONT>
</P>
<P><FONT SIZE=3D2>Is this correct? Thanks for pointing out the section =
of the man page I</FONT>
<BR><FONT SIZE=3D2>didn't quite get down to!</FONT>
</P>
<P><FONT SIZE=3D2>On Wed, 4 Feb 2004, Pat Lashley wrote:</FONT>
</P>
<P><FONT SIZE=3D2>> --On Wednesday, February 04, 2004 17:24:17 -0800 =
Erik Kline <kline at netapp.com> wrote:</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> >> =
Number: 62368</FONT>
<BR><FONT SIZE=3D2>> >> =
Category: conf</FONT>
<BR><FONT SIZE=3D2>> >> =
Synopsis: 5.2-RELEASE syslog.conf =
appears to be malformed</FONT>
<BR><FONT SIZE=3D2>> ></FONT>
<BR><FONT SIZE=3D2>> >> Description:</FONT>
<BR><FONT SIZE=3D2>> > /etc/syslog.conf contains the following =
lines at the tail end of the file:</FONT>
<BR><FONT SIZE=3D2>> ></FONT>
<BR><FONT SIZE=3D2>> > !startslip</FONT>
<BR><FONT SIZE=3D2>> > =
*.* &nbs=
p;  =
; =
=
/var/log/slip.log</FONT>
<BR><FONT SIZE=3D2>> > !ppp</FONT>
<BR><FONT SIZE=3D2>> > =
*.* &nbs=
p;  =
; =
/var/log/ppp.log</FONT>
<BR><FONT SIZE=3D2>> ></FONT>
<BR><FONT SIZE=3D2>> > These don't appear to be syntactically =
valid. Any entries appended</FONT>
<BR><FONT SIZE=3D2>> > after these aren't parsed and processed. =
CVSup today (04 Feb 2004)</FONT>
<BR><FONT SIZE=3D2>> > shows that /usr/src/etc/syslog.conf remains =
malformed.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> man syslog.conf:</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> Each block of =
lines is separated from the previous block by a program or</FONT>
<BR><FONT SIZE=3D2>> hostname =
specification. A block will only log messages corresponding =
to</FONT>
<BR><FONT SIZE=3D2>> the most recent =
program and hostname specifications given. Thus, with a</FONT>
<BR><FONT SIZE=3D2>> block which =
selects `ppp' as the program, directly followed by a block</FONT>
<BR><FONT SIZE=3D2>> that selects =
messages from the hostname `dialhost', the second block will</FONT>
<BR><FONT SIZE=3D2>> only log messages =
from the ppp(8) program on dialhost.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> A program =
specification is a line beginning with `#!prog' or `!prog' (the</FONT>
<BR><FONT SIZE=3D2>> former is for =
compatibility with the previous syslogd, if one is sharing</FONT>
<BR><FONT SIZE=3D2>> syslog.conf files, =
for example) and the following blocks will be associ-</FONT>
<BR><FONT SIZE=3D2>> ated with calls to =
syslog(3) from that specific program. A program spec-</FONT>
<BR><FONT SIZE=3D2>> ification for =
`foo' will also match any message logged by the kernel with</FONT>
<BR><FONT SIZE=3D2>> the prefix `foo: =
'. The `#!+prog' or `!+prog' specification works just</FONT>
<BR><FONT SIZE=3D2>> like the previous =
one, and the `#!-prog' or `!-prog' specification will</FONT>
<BR><FONT SIZE=3D2>> match any message =
but the ones from that program. A hostname specifica-</FONT>
<BR><FONT SIZE=3D2>> tion of the form =
`#+hostname' or `+hostname' means the following blocks</FONT>
<BR><FONT SIZE=3D2>> will be applied to =
messages received from the specified hostname. Alter-</FONT>
<BR><FONT SIZE=3D2>> natively, the =
hostname specification `#-hostname' or `-hostname' causes</FONT>
<BR><FONT SIZE=3D2>> the following =
blocks to be applied to messages from any host but the one</FONT>
<BR><FONT SIZE=3D2>> specified. =
If the hostname is given as `@', the local hostname will be</FONT>
<BR><FONT SIZE=3D2>> used. A =
program or hostname specification may be reset by giving the</FONT>
<BR><FONT SIZE=3D2>> program or =
hostname as `*'.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> The reason that lines added after that point =
don't appear to be</FONT>
<BR><FONT SIZE=3D2>> parsed or processed is that they apply only to =
messages from programs</FONT>
<BR><FONT SIZE=3D2>> named 'ppp'.</FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>></FONT>
<BR><FONT SIZE=3D2>> -Pat</FONT>
<BR><FONT SIZE=3D2>></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C3EB8C.896BD480--
More information about the freebsd-bugs
mailing list