hlu@phys1.physics.wsu.edu (Hongjiu Lu) writes:

quoted text
>Yes. It also happened to computers in our school. I sometimes got into someone
>else's account. They have fixed it now.

quoted text
>-- 
>H.J.
>Gcc/libc maintainer for Linux.
>In article <2960@ariel.its.unimelb.EDU.AU>, pdp@ariel.its.unimelb.EDU.AU (Paul Douglas Page) writes:
>|> without logging out correctly the session remains active so the next caller gets to coninue on with the previous callers session. It happens with both my internal and external modems so it's not a cable problem.
>|> Any suggestions?

If the shell doesn't die, there is not much that getty or anything else can
do about it. The getty process is long gone when the shell is started, and
will not be re-spawned until the shell dies.

On an dial-in line the shell should get a SIGHUP when the carrier drops, and
this should in most cases kill the shell.

        - Peter.

-- 
Peter Orbaek <poe@daimi.aau.dk>
Hasle Ringvej 122, DK-8200 Aarhus N, DENMARK