From owner-freebsd-bugs Tue Oct 29 10:10:03 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA14112 for bugs-outgoing; Tue, 29 Oct 1996 10:10:03 -0800 (PST) Received: (from gnats@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id KAA14105; Tue, 29 Oct 1996 10:10:02 -0800 (PST) Resent-Date: Tue, 29 Oct 1996 10:10:02 -0800 (PST) Resent-Message-Id: <199610291810.KAA14105@freefall.freebsd.org> Resent-From: gnats (GNATS Management) Resent-To: freebsd-bugs Resent-Reply-To: FreeBSD-gnats@freefall.FreeBSD.org, mi@aldan.ziplink.net Received: from rtfm.ziplink.net ([199.232.255.52]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id KAA13683 for ; Tue, 29 Oct 1996 10:01:44 -0800 (PST) Received: (from root@localhost) by rtfm.ziplink.net (8.7.5/8.7.3) id MAA08993; Tue, 29 Oct 1996 12:59:10 -0500 (EST) Message-Id: <199610291759.MAA08993@rtfm.ziplink.net> Date: Tue, 29 Oct 1996 12:59:10 -0500 (EST) From: mi@aldan.ziplink.net Reply-To: mi@aldan.ziplink.net To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.2 Subject: bin/1924: lpc's output erroneous and confusing Sender: owner-bugs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Number: 1924 >Category: bin >Synopsis: if lpd is not running, lpc will say ``no such file or directory'' >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Oct 29 10:10:01 PST 1996 >Last-Modified: >Originator: Mikhail Teterin >Organization: >Release: FreeBSD 2.2-960801-SNAP i386 >Environment: If lpd is not started, attempts to use ``lpc start lp'' will lead to : mi@rtfm:/mnt/root/invoice (128) lpc start lp lp: printing enabled lpc: connect: No such file or directory couldn't start daemon Instead of smth like: ``can not connect to lpd. Is it running?'' Or even better: ``lpd not running. Try to start it (y/n)?'' >Description: See above >How-To-Repeat: kill `ps -ax | grep lpd | awk '{print $1}'` lpc start lp >Fix: Seems like lpc relies on errno routines to report errors (perror()?) If I am wrong -- this is just another evidence of how confusing this output really is ;) BTW, I reported a similar problem with route(8), when the sysadmin- -beginner would sometimes get an error output with "Disk quota exceeded" instead of whatever is wrong really. Either perror() and stuff need to be fixed (serious and correct solution?), or things like lpc and route need to process errors on their own (quickier and dirtier solution?). It is hard to appreciate the advanced features of FreeBSD with bugs like this -- bugs contributing to the myth, that Unix is hard to understand. >Audit-Trail: >Unformatted: