Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!sol.ctr.columbia.edu!ira.uka.de!fauern!opal!tmpmbx!scuzzy!src
From: src@scuzzy.in-berlin.de (Heiko Blume)
Newsgroups: comp.unix.programmer
Subject: Re: List of routines safe to use in signals?
Message-ID: <1990Dec18.014429.8583@scuzzy.in-berlin.de>
Date: 18 Dec 90 01:44:29 GMT
References: <1990Dec12.050527.2152@athena.mit.edu> <1990Dec13.022804.7712@scuzzy.in-berlin.de> <1990Dec13.205957.25208@athena.mit.edu> <268
Organization: Contributed Software
Lines: 22

brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
>> The definition and purpose of a
>> specification in computer programming is that it tells you, as a programmer,
>> what YOU need to do and what the FUNCTION guarantees to do when you call it.

>Exactly. Like close() is guaranteed to return either 0 or -1 with EBADF
>or EINTR. Whether the file is local or over NFS, close() *guarantees*
>not to return anything else.

yeah!

close(2):

[ENOLINK]   Fildes is on a remote machine and the link to that machine
            is no longer active. (system V Release 3.2).

sounds adequate for NFS, but is for RFS as far as i know.
-- 
      Heiko Blume <-+-> src@scuzzy.in-berlin.de <-+-> (+49 30) 691 88 93
                    public source archive [HST V.42bis]:
        scuzzy Any ACU,f 38400 6919520 gin:--gin: nuucp sword: nuucp
                     uucp scuzzy!/src/README /your/home