Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!oliveb!sun!limes
From: limes@sun.uucp (Greg Limes)
Newsgroups: comp.unix.wizards
Subject: Re: Problems in shutting down a Sun
Message-ID: <50282@sun.uucp>
Date: 21 Apr 88 02:10:09 GMT
References: <8558@oberon.USC.EDU>
Organization: Sun Microsystems, Inc. - Mtn View, CA
Lines: 30
Summary: an idea, maybe ...

In article <8558@oberon.USC.EDU>, mcooper@acamar.usc.edu (Michael A. Cooper) writes:
> 
> [ We are running SunOS 3.2 and 3.4 on Sun-3's. ]
> 
[lots of stuff hacked out]

> If I change my program to:
> 
> 	kill(1, SIGTERM);
> 
> all processes (including my process) except system processes get
> SIGTERM and everything works fine, including when I'm running
> Suntools.  This is the way the 4.3BSD shutdown does it.  This way
> works, except I can't do anything after I do this since my own process
> gets killed.

DISCLAIMER: While I work at SUN, I have not (yet) examined the sources
to shutdown, so I do not have any idea precisely what it does.

But, Mike, you can always simply catch the signal ... try
	signal (SIGTERM, SIG_IGN)
before the kill; your program will quietly burp as it eats the SIGTERM
and continues executing.

> Michael A. Cooper, University Computing Services, U of Southern California
>   UUCP: {sdcrdcf, cit-vax}!oberon!mcooper   BITNET: mcooper@kylara
>   ARPA: mcooper@oberon.USC.EDU              PHONE: (213) 743-2957


-- Greg Limes [limes@sun.com]			frames to /dev/fb
   I do not speak for Sun. I barely speak for myself.