Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!ucla-cs!dgreen
From: dgreen@ucla-cs.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: du's "--bad status" message
Message-ID: <5480@shemp.UCLA.EDU>
Date: Fri, 10-Apr-87 02:40:44 EST
Article-I.D.: shemp.5480
Posted: Fri Apr 10 02:40:44 1987
Date-Received: Sat, 11-Apr-87 14:00:04 EST
References: <880@maynard.BSW.COM> <434@yabbie.oz>
Sender: root@CS.UCLA.EDU
Reply-To: dgreen@CS.UCLA.EDU (Dan R. Greening)
Lines: 19

In article <434@yabbie.oz> rcodi@yabbie.oz (Ian Donaldson) writes:
>In article <880@maynard.BSW.COM>, campbell@maynard.BSW.COM (Larry Campbell) writes:
>> 	du /usr/spool/news | sort -nr
>> 	--bad status < /usr/spool >
>> 	--bad status < /usr/spool >
>
>It probably means you don't have permission to access /usr/spool (not root?).

It may also mean that you have hard-linked some directories.  You might get 
bad status from "link", if the link count on the directory and the number of 
sub-files aren't equal.  Not-equal means bad things... "find" descending a 
hard-linked directory won't be able to ascend properly.

At least I've had this problem... after (incorrectly) using /etc/link to link
directories.


 _D_a_n_ _G_r_e_e_n_i_n_g     _A_R_P_A-  dgreen@CS.UCLA.EDU
                  _U_U_C_P- ..!{sdcrdcf,ihnp4,trwspp,ucbvax}!ucla-cs!dgreen