From owner-freebsd-hackers  Sun Jan 28 08:55:35 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id IAA21781
          for hackers-outgoing; Sun, 28 Jan 1996 08:55:35 -0800 (PST)
Received: from Aspen.Woc.Atinc.COM (aspen.woc.atinc.com [198.138.38.205])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA21776
          for <freebsd-hackers@freebsd.org>; Sun, 28 Jan 1996 08:55:30 -0800 (PST)
Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id LAA12857; Sun, 28 Jan 1996 11:54:26 -0500
Date: Sun, 28 Jan 1996 11:54:24 -0500 (EST)
From: "Jonathan M. Bresler" <jmb@freebsd.org>
X-Sender: jmb@Aspen.Woc.Atinc.COM
To: Joerg Wunsch <joerg_wunsch@uriah.heep.sax.de>
cc: FreeBSD hackers <freebsd-hackers@freebsd.org>
Subject: Re: sysexits.h. which EX_ to use
In-Reply-To: <199601280943.KAA01284@uriah.heep.sax.de>
Message-ID: <Pine.BSF.3.91.960128115032.12847A-100000@Aspen.Woc.Atinc.COM>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
Precedence: bulk

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