Re: bin/58558: syslog.conf(5) man page example does not work.

[xover2391%hush.com@localhost]

On 8/9/2024 at 6:05 AM, xover2391%hush.com@localhost wrote:
>
>The following reply was made to PR bin/58558; it has been noted by 
>GNATS.
>
>From: xover2391%hush.com@localhost
>To: gnats-bugs%netbsd.org@localhost, gnats-admin%netbsd.org@localhost, netbsd-
>bugs%netbsd.org@localhost
>Cc: 
>Subject: Re: bin/58558: syslog.conf(5) man page example does not 
>work.
>Date: Fri, 09 Aug 2024 06:03:40 +0000
>
> On 8/7/2024 at 2:35 PM, "Michael van Elst" <mlelstv%serpens.de@localhost> 
>wrote:
> >
> >The following reply was made to PR bin/58558; it has been noted 
>by 
> >GNATS.
> >
> >From: mlelstv%serpens.de@localhost (Michael van Elst)
> >To: gnats-bugs%netbsd.org@localhost
> >Cc: 
> >Subject: Re: bin/58558: syslog.conf(5) man page example does not 
> >work.
> >Date: Wed, 7 Aug 2024 14:31:03 -0000 (UTC)
> >
> > xover2391%hush.com@localhost writes:
> > 
> > >Yes, I am aware of this. Of the four lines I added to 
> >/etc/syslog.conf, I am assuming that it only matters to the last 
> >one, and the space between the *.* and /var/log/foreign is tabs 
> >not spaces.
> > 
> > I have configured something similar (netbsd-10/i386) and it 
>just 
> >works.
> > One difference is that I don't use the !* program 
>specification. 
> >It's
> > 
> > +@
> > ... local rules here ...
> > -@
> > ... remote rules here ...
> > 
> > And I tested that adding !* like in the example doesn't change 
> >the behaviour.
> 
> Although I'm trying to get the syslog messages from a HP network 
>switch written to a separate file in /var/log on a NetBSD-10/amd64 
>server, I'm happy to try different things to try and figure out 
>what's going wrong with that. I can do what you've suggested, and 
>also try doing it from a computer running NetBSD, and to a server 
>running NetBSD/i386, to see if I can get the same results. If I 
>can get success with that, I can then try and sort out the problem 
>with the HP switch.
> 
> I can try this out next week when I am back on-site.
> 
> Thanks.

It's taken me longer than I would have liked to get back to this. Apologies for keeping this open longer than it needed to be.

I thought of something that I don't normally do when I'm installing NetBSD, and which was something that I did not do here. I don't normally bother with assigning a hostname.

When I added the following to /etc/rc.conf:

hostname="netbsd1"

and then rebooted, I saw that the /var/log/foreign file was now only being used to store the syslog messages coming from the remote device.

Clearly, the assigning of a hostname is required so it can operate in the way I want it to and expect it to.

I greatly appreciate the suggestion given earlier about using "+@" and "-@" to explicitly separate the local and remote rules.

Many thanks to all who helped on this one.

This can now be closed.