Sun Managers,
As luck would have it, I discovered the answer shortly after sending the email message. The problem was that inetd needed the -t (trace) flag in order for other daemon processes to log through syslog. My explanation may not be academically correct, but through inspection this seems to be the case.
To solve the problem, I edited the /etc/init.d/inetsvc with the following:
/usr/sbin/inetd -t -s &
After killing inetd and restarting from inetsvc all is working well.
Duane Gran
Solaris Central - http://www.SolarisCentral.org
>
> Sun Managers,
>
> I am hoping that someone might be able to shed some light on a peculiar message in my /var/adm/messages file. Below is a transcript of the file:
>
> Mar 23 12:04:34 holst inetd[115]: 100234/rpc/ticotsord version 1: rpcb_set: not started
> Mar 23 12:09:16 holst inetd[115]: 100234/rpc/ticotsord version 1: rpcb_set: not started
> Mar 23 13:55:53 holst inetd[115]: 100234/rpc/ticotsord version 1: rpcb_set: not started
>
> My original intention was to get ftp logging to the messages file. I have given in.ftpd the -l switch and have restarted inet.d. I have confirmed that daemon.notice is logging to /var/adm/messages and have restarted syslogd.
>
> I notice a curious behavior when I restart inetd and initiate an ftp connection. The first ftp connection takes about 2 minutes before the login prompt appears. I believe the inetd[115] messages noted above are trying to tell me something, but I'm not sure. I disabled several RPC services for security reasons, but I am interested to know if I broke the ftp logging facility.
>
> I looked through the Sun Manager's archive but didn't find anything explaining this message. Any insight on this is greatly appreciated, and I will return the favor with a detailed summary.
>
> Duane Gran
> Solaris Central - http://www.SolarisCentral.org
>
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:05 CDT