Date: Tue, 29 Oct 1996 12:30:01 -0800 (PST) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-bugs Subject: Re: bin/1924: lpc's output erroneous and confusing Message-ID: <199610292030.MAA21540@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/1924; it has been noted by GNATS.
From: J Wunsch <j@uriah.heep.sax.de>
To: mi@aldan.ziplink.net
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/1924: lpc's output erroneous and confusing
Date: Tue, 29 Oct 1996 21:15:30 +0100 (MET)
As mi@aldan.ziplink.net wrote:
> printing enabled
> lpc: connect: No such file or directory
> Seems like lpc relies on errno routines to report errors (perror()?)
It does. To the used sysadmin (or programmer?), the little word
`connect:' indicates the real source of the error: there's no local
domain socket to connect to (i.e., /var/run/printer doesn't exist,
hence "No such file or directory" is indeed appropriate).
This might probably be re-worded, but i see it as very low priority.
There are too many things of this kind, and it would probably bloat
the source by quite some bits to special case all eventual meanings of
various error messages. (Apart from this, somebody must actually do
it.) perror() is fairly simple, while something like:
if (errno == ENOENT)
fprintf(stderr, "No server is running.\n");
else if (errno = EMUMBLE)
fprintf(stderr, "Some fooish must have happened.\n");
...
else
perror("connect");
seems to be much effort.
--
cheers, J"org
joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199610292030.MAA21540>