Path: utzoo!attcan!uunet!zephyr.ens.tek.com!gvgpsa!treehouse!andyp
From: andyp@treehouse.UUCP (Andy Peterman)
Newsgroups: comp.sys.mac.misc
Subject: Re: Mac OS versus A/UX, Who runs under who?
Message-ID: <631@treehouse.UUCP>
Date: 5 Nov 90 05:23:56 GMT
References: <{'!^2|*@rpi.edu> <627@treehouse.UUCP> <1990Nov5.004631.20821@smsc.sony.com>
Organization: The Tree House
Lines: 25

In article <1990Nov5.004631.20821@smsc.sony.com> dce@smsc.sony.com (David Elliott) writes:
>
>In article <627@treehouse.UUCP> andyp@treehouse.UUCP (Andy Peterman) writes:
>>which simply kills the MacOS process and logs you out, all without
>
>Wait.  I don't think you mean "logs you out", at least not in the Unix
>sense of the term.  I mean, if a bombed MacOS program actually logged
>me out of my A/UX session, it would be only slightly better than
>having the whole system go down.

It depends on how bad the bomb is.  If its just an application bomb
where under the normal MacOS you could ExitToShell and keep running,
then the same holds true under A/UX.  But if you completely bomb the
system where normally you would end up rebooting, then yes, you are
"logged out".  I believe this is due to the fact that when you log in,
you're actually logging in to the MacOS and the CommandShell is simply a
secondary shell.  If you bomb MacOS, not just some application, then
A/UX has no other choice than to kill it, which logs you out.  Any other
processes, such as anyone else logged in through the serial ports, will
continue normally.

-- 
Andy Peterman                       |   Opinions expressed
treehouse!andyp@gvgpsa.gvg.tek.com  | are definitely those of
(916) 273-4569                      |      my employer!