The problem was corrupted svc.conf file. I don't now why this file didn't
have all entries but this is why inetd couldn't start any service which is
using sockets. Syslog uses one udp port also and that's why it didn't start.
Many thanks to Simon Greaves, Oisin McGuinness and Serguei Patchkovskii who
all showed me the proper direction where to look.
Sasa
-----Original Message-----
From: Aleksandar Stojiljkovic <aleks_at_eurocom.co.yu>
To: tru64-unix-managers_at_ornl.gov <tru64-unix-managers_at_ornl.gov>
Date: 13. maj 1999 13:53
Subject: syslogd not starting
>Hi,
>
>During boot process (and when I try to start it manualy) syslogd says:
>
>(machine) syslogd: syslog/udp: unknown service
>
>Now, I have properly configured /etc/services, there is OK syslog.conf and
>there is /dev/klog character device with proper permissions. I looked on
>another machine where syslog is working and everything is the same (the
only
>difference is that syslogd is running :))
>
>On problematic machine (AS 4100) I have DU4.0D (no patches), there is
>TruCluster 1.5 Production Server too which doesn't work for now but this is
>another problem.
>
>Related with syslogd error is that inetd reports that can't find tcp and
udp
>ports.
>
>Another cluster machine which is identical is working fine. I tried to copy
>syslogd binary and kernel but this didn't help.
>
>Can anyone help me?
>
>Regards,
>Sasa
>
>
>=============================================
>Euro Com d.o.o Belgrade (info_at_eurocom.co.yu)
>Obilicev venac 26 tel: +381/11-638007
>11000 Belgrade +381/11-638341
>Yugoslavia fax: +381/11-185286
>=============================================
>
Received on Thu May 27 1999 - 07:07:07 NZST