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.

> On Mon, Oct 04, 1999 at 07:09:59AM -0400, Jt Chiodi wrote:
> > I am getting a (: not found with the daily script.
> > the only parenthesys are in the find core part of the script.
> > Is this another link to /bin/test? I don't remember removing a (.
> 
> Sounds more like that's the Bourne shell wanting you to put
> parantheses around something that doesn't have them... but I'm not so
> sure.
> 
> Possibly you've got a stray (, and all sh can interpret as is an
> executable call, and it can't find an executable named (?
> 
> My mac68k machine is disabled currently and my macppc machine doesn't
> seem to have this problem with 1.4.1.
> 
> You might try breaking chunks of your daily script off and running
> them by hand to see if you can narrow down where the problem is.
> 
>        ~ g r @ eclipsed.net
> 





_______________


Jt Chiodi
Unix Administrator
University of Pittsburgh
chiodi@pitt.edu