Not a defunct process, what is the problem?

[babeo]

Hello,

I have probem with telnet process on my unix box. I reboot the box, and start the application, I see the in.telnetd process running on this box , I believe it is similar to have /usr/sbin/cron process running, so that every time when a telnet task kicks in, it will auto telnet and connect to a destination. The problem is the telnet session is openned and could not closed, and is hanging on the OS, so I have more than 30 old telnet processes still open. What is the cause of this problem?

2) I have another question: How can I trace an output file that is kept producing by a process, but I could not seen it in crontab?

Thanks

 

[daFranze]

1) what Solaris Version are you running? This might be a bug (fix this with a patch)

2) I need more info, I do not understand the question...

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years

 

[babeo]

Hi Franz,
1) Solaris 8
2) ls -l /proc, and I see many subdirectories contains "as" files, which I check from manual is "assembly" file, and it is an output file, I just want to know what process that producing these "as" files, some of them are automatically removed themselves, some don't.

Thanks

 

[daFranze]

Hi babeo

1) check the patches for telnet, ip, tcp, all around networking...
the easiest way to do this is download patchdiag tool from sunsolve.sun.com and patchdiag.xref and run the tool; it will show you the installed version of software and the latest patchrelease

2) /proc is of Filesystemtype procfs, so lsof etc. won't work. I never debugged things like that, maybe you can find something in man procfs or the bins in /usr/proc/bin can help?

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years