home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!news
- From: sweet@skat.usc.edu (Rob Sweet)
- Newsgroups: comp.sys.next.sysadmin
- Subject: Behavior of OD at logout
- Date: 22 Jul 1992 00:56:57 -0700
- Organization: University of Southern California, Los Angeles, CA
- Lines: 32
- Sender: sweet@skat.usc.edu (Rob Sweet)
- Message-ID: <l6q569INNlj5@skat.usc.edu>
- NNTP-Posting-Host: skat.usc.edu
-
- I am using a 68040 NeXT cube that is tied into our network
- file serving and account service. I do not have root access, and I
- login (usually at the console) via my "network" account. When using
- an optical disk, that disk essentially becomes "owned" by whoever is
- logged in at the console. When logging out, the optical disk USUALLY
- is ejected. On the few occasions that it did not eject, I'm sorry to
- say I didn't remotely check what the ownership of the disk became.
- Also, when trying to eject for changing optical disks, I often get a
- "Disk Busy. Can't Eject." message. The "Processes" window shows no
- applications or background processes that were launched from the OD.
- This problem usually requires logging out in order to eject the disk.
-
- I would like to know if there is:
-
- 1. A way to keep the OD from ejecting at logout and keep some directories
- private access and leave others group or public access.
-
- and/or
-
- 2. A reliable way to eject and change OD's without logging out.
-
- As stated earlier, I do not have root access, and I really
- don't know much on the sysadmin level. Please respond via E-mail and
- I will post a summary if there is interest. Sorry, but I don't have
- NeXTMail. I am not sure why not, but that's another question.
-
- Thanks a meg.
-
- Rob Sweet sweet@skat.usc.edu
-
- "If the first step in a long journey is the most difficult, what is
- the NeXTStep?" - RS
-