Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!gatech!hao!oddjob!gargoyle!ihnp4!homxb!ho95e!wcs From: wcs@ho95e.ATT.COM (Bill.Stewart) Newsgroups: comp.unix.questions Subject: Re: Disabling logins under System V Message-ID: <1534@ho95e.ATT.COM> Date: Wed, 15-Jul-87 20:00:19 EDT Article-I.D.: ho95e.1534 Posted: Wed Jul 15 20:00:19 1987 Date-Received: Sat, 18-Jul-87 04:13:57 EDT References: <905@woton.UUCP> <632@ora.UUCP> Reply-To: wcs@ho95e.UUCP (46133-Bill.Stewart,2G218,x0705,) Organization: AT&T Bell Labs 46133, Holmdel, NJ Lines: 22 In article <905@woton.UUCP>, riddle@woton.UUCP (Prentiss Riddle ) writes: : I am looking for some advice about the preferred way to temporarily : disable all user logins under System V. : ...I want a simple, reversible solution : that can be run by the person who comes in on weekends to do our : backups. Sounds like you've got two problems: how to keep people from logging in, and what to do about programs already running. The latter is hard to do well (if you kill them, you have to notify the users, and hope they don't mind.) The "fuser" command is one way to kill off processes. For users who use /bin/sh or ksh, you can put the following in /etc/profile: if [ -f /etc/nologin -a "$LOGNAME" != "root" ] then echo "Sorry, the system is not available" ; exit fi You've also got to turn off incoming uucp; you could chmod 0 uucico or something. (If you're not backing up /usr, and you're restricting uucp permissions, you could just leave it on.) -- # Bill Stewart, AT&T Bell Labs 2G-202, Holmdel NJ 1-201-949-0705 ihnp4!ho95c!wcs