Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!usc!ucsd!ucbvax!bloom-beacon!eru!hagbard!sunic!kullmar!pkmab!ske
From: ske@pkmab.se (Kristoffer Eriksson)
Newsgroups: comp.unix.internals
Subject: Re: Trojan Horses
Message-ID: <4357@pkmab.se>
Date: 26 Oct 90 07:40:09 GMT
References: <5238:Oct2322:14:3690@kramden.acf.nyu.edu> <1893@necisa.ho.necisa.oz> <8645:Oct2521:49:5790@kramden.acf.nyu.edu>
Organization: Peridot Konsult i Mellansverige AB, Oerebro, Sweden
Lines: 17

In article <8645:Oct2521:49:5790@kramden.acf.nyu.edu> brnstnd@kramden.acf.nyu.edu (Dan Bernstein) writes:
> Tell me: Why should I handle EDQUOT? Why should I interpret it
>as some sort of error? Who benefits if I thrash about upon this error?

As the user of a program I expect it to report ALL unexpected errors,
no matter whether the program knows how to recover from them or not.
*I* might be able to correct the error situation, and most importantly,
I absolutely demand to be informed if my data possibly did not make it
to the disk. That the program doesn't know how to recover from the error
is no excuse for not telling me about it. After all, there's no problem
detecting that there was some kind of error, the only problem occurs if
you absolutely must have the program automatically recover from the error
without involving the user.
-- 
Kristoffer Eriksson, Peridot Konsult AB, Hagagatan 6, S-703 40 Oerebro, Sweden
Phone: +46 19-13 03 60  !  e-mail: ske@pkmab.se
Fax:   +46 19-11 51 03  !  or ...!{uunet,mcsun}!sunic.sunet.se!kullmar!pkmab!ske