Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site allegra.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mp
From: mp@allegra.UUCP (Mark Plotnick)
Newsgroups: net.bugs.4bsd,net.unix-wizards
Subject: rlogind and background processes
Message-ID: <2890@allegra.UUCP>
Date: Thu, 8-Nov-84 12:17:03 EST
Article-I.D.: allegra.2890
Posted: Thu Nov  8 12:17:03 1984
Date-Received: Fri, 9-Nov-84 08:40:15 EST
Organization: AT&T Bell Laboratories, Murray Hill
Lines: 13

rlogind sends a signal 9 to all processes in the user's login process
group when the user logs out.  If the user uses /bin/sh, then the
user's entire process tree, including background uucico's and sendmail's,
gets creamed.  This is less than optimal.  Is there any reason why
the following wouldn't work?
   - in rlogind.c, change kill(0, SIGTERM) to kill(0, SIGHUP)
   - in login.c, add a signal(SIGHUP,SIG_DFL) before the user's
     login shell is invoked.  This is necessary because getty's and
     login's that are invoked from daemons (such as rlogind and chserver)
     apparently have SIGHUP ignored.

	Mark Plotnick
	Society for the Prevention of Cruelty to Processes