Date: Sun, 28 Jan 1996 11:54:24 -0500 (EST) From: "Jonathan M. Bresler" <jmb@freebsd.org> To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de> Cc: FreeBSD hackers <freebsd-hackers@freebsd.org> Subject: Re: sysexits.h. which EX_ to use Message-ID: <Pine.BSF.3.91.960128115032.12847A-100000@Aspen.Woc.Atinc.COM> In-Reply-To: <199601280943.KAA01284@uriah.heep.sax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 28 Jan 1996, J Wunsch wrote: > MHO: EX_IOERR for read/write/fclose > EX_OSERR for fstat (stat'ing should always be possible if the > file exists) good. now what about an unlink(2) call. it can fail for several reasons. permissions (EPERM -> EX_NOPERM). access rights (EACCESS -> EX_NOPERM). bad arguments (ENOTDIR, EINVAL, ENAMETOOLONG, ENOENT -> EX_USAGE). excess number of symlinks (ELOOP -> EX_OSERR). well you get the idea. what should the program that calls unlink(2) use for err(2) ?? jmb Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.91.960128115032.12847A-100000>