Hello,
I have been experiencing a strange problem for some time with inetd.conf
being emptied. When it happens, inetd.conf exists but there is nothing in
it. I've not modified the inetd.conf or any other inetd files, and
inetd.local and inetd.conf.local still look like as they are by default.
The result of course is that any e.g. telnet or ftp connections are getting
refused. It took me some time to figure out what was wrong, and even "rcinet
restart" did not show any problem and it looked like all daemons were
started.
The problem appeared under version Tru64 5.1 on a DS20, and now also under
Tru64 5.1A on an ES40. The only thing I can remember having done prior to
the problem is to issue init commands, e.g. init 0, init 2, init s, followed
by a normal boot from the system console.
The problem does not seem easy to reproduce or is sporadic, and it might
have something to do with some other configurations, such as /tmp lsm
partition, audit and enhanced security.
Has anyone else experienced the problem or knows more about it.
Thanks and best regards,
RFE/RL, Inc,
Markus Waldorf
Received on Tue Jun 10 2003 - 09:46:54 NZST