OpenServer 5.0.6 syslogd won't take remote messages

[Hillel]

Hello All,

We just upgraded one of our servers from OpenServer 5.0.4c to 5.0.6.
There are a number of 5.0.4 clients (created with the Embedded
Configuration Toolkit) that need to log their system messages to this
server.
Each has a properly configured /etc/syslog.conf file. There was no
problem when the server was running OpenServer 5.0.4, but now the
5.0.6 server will not accept any syslog messages from other systems.

For testing, the client systems will log their messages to the syslog on
our other servers running OpenServer 5.0.5 and 5.0.4. Testing with the
other
servers shows that the 5.0.6 server will not accept remote syslog messages
even from the other servers, although the 5.0.5 and 5.0.4 systems can log
the messages to each others' syslog files.

Port 514/udp is set up for syslog in /etc/services.

Is there anything in OpenServer 5.0.6 that will block syslog messages
from remote systems differently than in previous versions of OpenServer?
As of version 5.0.5, it was supposed to be impossible to stop a
server from receiving those messages without removing the
514/udp line in /etc/services.

Thanks.
---Hillel

[Bela Lubkin]

Hillel wrote:

> We just upgraded one of our servers from OpenServer 5.0.4c to 5.0.6.
> There are a number of 5.0.4 clients (created with the Embedded
> Configuration Toolkit) that need to log their system messages to this
> server.
> Each has a properly configured /etc/syslog.conf file. There was no
> problem when the server was running OpenServer 5.0.4, but now the
> 5.0.6 server will not accept any syslog messages from other systems.

> As of version 5.0.5, it was supposed to be impossible to stop a

> server from receiving those messages without removing the
> 514/udp line in /etc/services.

A new flag was added to syslogd: "-r". Without this flag, 5.0.6 syslogd
does not accept remote messages. For your purposes you need to add the
flag. I quote the 5.0.6 syslogd(ADM) man page:

" syslogd can read from:

...

" o When the -r option is specified, a remote host using an Internet domain
" socket bound to port 514; see services(SFF)

...

" syslogd understands the following options:

...

" -r service messages from remote systems (via syslog port).

>Bela<

[Hillel]

Thanks. It works with the "-r" flag.
Now, how do I get it to automatically start with this flag?

I added the "-r" flag to the line with the "/etc/syslogd" command in
/etc/rc2.d/S85tcp. After rebooting, the syslog still does not accept
remote requests. The "ps" command shows "syslogd" running
without the "-r" flag.

---Hillel

Bela Lubkin wrote in message
<2001091613...@mammoth.ca.caldera.com>...

[Bela Lubkin]

Hillel wrote:

> Thanks. It works with the "-r" flag.
> Now, how do I get it to automatically start with this flag?
>
> I added the "-r" flag to the line with the "/etc/syslogd" command in
> /etc/rc2.d/S85tcp. After rebooting, the syslog still does not accept
> remote requests. The "ps" command shows "syslogd" running
> without the "-r" flag.

S85tcp only starts syslogd if it isn't already running; which it
normally is. It's actually started by /etc/bcheckrc, so you'll want to
make the same change there. (We ought to ship both scripts with
comments on how they interact...)

>Bela<

[Hillel]

Thanks. Seems to work properly now.

---Hillel

Bela Lubkin wrote in message

<2001091719...@mammoth.ca.caldera.com>...