Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!bu.edu!nntp-read.bu.edu!robertl
From: robertl@bucsf.bu.edu (Robert La Ferla)
Newsgroups: comp.sys.next
Subject: find bug (was re: Clearing out old .NeXTtrash files)
Message-ID: <ROBERTL.90Apr11041157@bucsf.bu.edu>
Date: 11 Apr 90 08:11:57 GMT
References: <8870@lindy.Stanford.EDU> <90100.170123CMH117@psuvm.psu.edu>
Sender: news@bu.edu.bu.edu
Organization: Boston University Computer Science Department
Lines: 20
In-reply-to: CMH117@psuvm.psu.edu's message of 10 Apr 90 21:01:23 GMT

In article <90100.170123CMH117@psuvm.psu.edu> CMH117@psuvm.psu.edu (Charles Hannum) writes:

[lines deleted]

>      foreach d (`find / -name ".NeXTtrash" -type d -print`)
>	 rm -r $d/*
>      end
>
>   (Note:  You'll want to redirect stderr when you do this!!)

Has anyone mentioned the bug in find yet?  The error message for a
non-accessible directory/file is missing a new line so the multiple errors
get printed on the same line.  Very hard to read and bad for shell scripts
that may want to cull through this information.  So, NeXT, did you find the
bug in find?  Couldn't resist.

   __  
  /  \      /         __/_
 /___/ __  /_  __  __  /	INTERNET:	robertl@bucsf.bu.edu
/ \   '_' /_/ |_- / ' /		BITNET:		mete0pc@buacca.bu.edu