Subject: Re: getting error with daily script
To: Jt Chiodi <chiodi+@pitt.edu>
From: gabriel rosenkoetter <gr@eclipsed.net>
List: port-mac68k
Date: 10/04/1999 09:48:25
On Mon, Oct 04, 1999 at 09:35:25AM -0400, Jt Chiodi wrote:
> I isolated the troubled code as you suggested.  here it is:
> 
>         find / \( ! -fstype local -o -fstype rdonly -o -fstype fdesc \
>                 -o -fstype kernfs -o -fstype procfs \) -a -prune -o \
>                 -name 'lost+found' -a -prune -o \
>                 -name '*.core' -a -print > $TMP
>                 \( -name '[#,]*' -o -name '.#*' -o -name a.out \
>                    -o -name '*.CKP' -o -name '.emacs_[0-9]*' \) \
>                         -a -atime +3 -exec rm -f -- {} \; -a -print > $TMP
> The output is (:
> As you can see the parens are matched.  I have not changed this code
> in the daily script and it has worked in the past.

I can't see anything specifically wrong with that call to find.

Do you have more than one find binary on your system? Have you changed
PATH for the daily script at all?

(If you don't understand what that's doing, btw, it'd be a good idea
to read the find(1) man page some time - it's fairly complicated but
extremely powerful.)

Also, just for the hell of it (as root) try find / -name ( -print

       ~ g r @ eclipsed.net