next message in archive
no next message in thread
previous message in archive
Index of Subjects
After verififying with David Trueman that there should be no Lynx process running without a controlling tty, I have upgraded 'pkiller' to detect this situation and to kill off the lynx process. 'pkiller' runs from csuite-cron every 15 minutes, so the wild "hit numbers" will still run up somewhat, but not nearly as high as had been the case. I will remind you that the true problem is with 'telnetd', which provides you with the connection to WWHCN in all cases. Quoting Larry Brinton from an earlier email: "I don't know why telnetd dies, it's the one that comes with all 2.0.x Linuxes. I've seen this happen in all versions of Linux. It has to be some kind of timeout caused by latency between the client and server, I don't have the source code. If Chebucto has a Linux box, they should be experiencing the same symptoms." David T. has the opinion that the Sun version of "telnetd" is more robust, and succeeds (mostly) in stopping all processes started by the telnet connection. Chebucto does not experience the problem as frequently because (besides being a Sun system) the modem lines are directly connected and 'telnetd' does not come into the picture. Gerard MacNeil, P. Eng.
next message in archive
no next message in thread
previous message in archive
Index of Subjects