I installed a dial-up modem at a client's office last week, and was puzzled by a problem that perhaps others have encountered: Just about everything seems to work perfectly fine, both in terms of hardware and software, for dialing into the Linux box. (He's running a recent version of Caldera that seems equivalent to Red Hat 5.0.) The line in /etc/inittab is set correctly, getty_ps works just fine for dial-in users, and the getty process respawns correctly after a user logs out. The hitch is that getty doesn't seem to respawn after a user with a shell logs in. That is, most of the users on this system have their shell set to be /usr/bin/pine. So someone can dial into the server from home, check his or her mail, and log out -- and everything will work just fine. When the system administrator decides to log in (not under "root," but another username), he is able to do whatever he wants as well. But as soon as he logs out, the modem hangs. I was able to reproduce this consistently. Getty exits and respawns just fine after logouts from users whose shell is set to /usr/bin/pine, but hangs (and requires HUPping init) after logouts from users whose shell is set to /bin/bash. I must admit that I'm rather stumped on this one. What is the difference between logging out from an interactive shell and a program like pine? Do we need to set an environment variable in bash? Do we need to set a new parameter for getty? If this were happening to all users, I would blame getty, but it's only happening on interactive shells. Any ideas? Reuven -- PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES! http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe" as the Subject.
