To fix this was as simple as commenting out the line in inetd.conf that
called rpc.ttdbserverd, and sending a HUP to the inetd process.
The default inetd.conf has three lines at the bottom related to CDE, even
though CDE was not installed on the workstation. I have commented all
three out, just in case. I am still not quite sure why a telnet session
calls rpc.ttdbserverd, and what it actually does.
Many thanks to:
Matt Harrington <matth_at_itsa.ucsf.edu>
Martin Mokrejs <mmokrejs_at_natur.cuni.cz>
John Speno <speno_at_isc.upenn.edu>
Sean O'Connell <sean_at_stat.Duke.EDU>A
Regards,
Garry.
Original message:
On Thu, 21 Jan 1999, Garry Optland wrote:
> I have just installed DU4.0E on a PW433au. This machine is going to
> replace our current proxy server running DU3.2 on a AS2000/166.
>
> I have installed the operating system mandatory subsets via a terminal
> with no graphics card in the machine. CDE was not a mandatory subset.
>
> When I log into the machine, everything is OK. However, if I telnet to
> localhost or to `hostname`, I get the following error message repeated on
> the console:
>
> Jan 21 16:24:02 inetd[30493]: execv /usr/dt/bin/rpc.ttdbserverd: no such
> file or directory.
>
> Each error line will have a different process ID, indicating that inetd
> is spawning itself. When I can get a spare process, "ps -ef | grep -c
> inetd" shows about 260 inetd processes.
>
> Does anyone know what rpc.ttdbserverd does, and why it is being called
> when CDE is not installed. Any hints on how to fix this would be greatly
> appreciated.
>
Received on Mon Jan 25 1999 - 01:34:14 NZDT