home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.programmer
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!mips!decwrl!pa.dec.com!decprl!decprl!boyd
- From: boyd@prl.dec.com (Boyd Roberts)
- Subject: Re: Process & Signal Question
- Message-ID: <1992Aug19.191008.19362@prl.dec.com>
- Sender: news@prl.dec.com (USENET News System)
- Nntp-Posting-Host: prl313.prl.dec.com
- Organization: Digital Equipment Corporation - Paris Research Laboratory
- References: <1657227@bailey.UUCP> <Bt5tp0.9JI@gumby.ocs.com> <shj.714240376@login.dkuug.dk>
- Date: Wed, 19 Aug 1992 19:10:08 GMT
- Lines: 18
-
- In article <shj.714240376@login.dkuug.dk>, shj@login.dkuug.dk (Stig Jacobsen) writes:
- > True. Well, mostly. This may be a bug in the NFS implementation
- > we're using, but if the binary is opened via NFS, you can unlink
- > the file locally on the machine where the file resides. Odd.
- >
-
- It's not odd if you know something about the implementation of NFS.
- The server knows nothing about which files are being executed remotely.
- Executables are read from the server, which explains why NFS imported
- executables must be readable by the invoker. Should such an executable
- be removed on the server the process executing it on the server will
- _probably_ die, depending on the executable's magic no and its memory
- state.
-
-
- Boyd Roberts boyd@prl.dec.com
-
- ``When the going gets wierd, the weird turn pro...''
-