Path: utzoo!utgpu!water!watmath!clyde!rutgers!sri-unix!quintus!sun!pitstop!sundc!seismo!uunet!mcvax!unido!pcsbst!jh
From: jh@pcsbst
Newsgroups: comp.unix.wizards
Subject: Re: What to do when close() fails? - (nf)
Message-ID: <4300011@pcsbst.UUCP>
Date: 12 Feb 88 08:30:00 GMT
References: <181@ateng.UUCP>
Lines: 14
Nf-ID: #R:ateng:-18100:pcsbst:4300011:000:547
Nf-From: pcsbst!jh    Feb 12 09:30:00 1988
Posted: Fri Feb 12 09:30:00 1988

Freeing the file descriptor is the first job done
by the UNIX SVR3 close() system call. Thus, you may reuse
it. Whatever happens else is the responsibility of the kernel.

Since I have seem some code in which u.u_error was tested in the kernel
[ after some operations like bread() ] I would strictly advise
against a driver close function to return an error code!
If the error condition is severe I would recommend a console
message from inside the kernel.

Note, that the close() code is protected from signals.

	Johannes Heuft
	unido!pcsbst!jh