Path: utzoo!utgpu!cunews!bnrgate!brtph3!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: jjd@alexander.bbn.com (James J Dempsey)
Newsgroups: comp.sys.sun
Subject: root crontab bug?
Keywords: Miscellaneous
Message-ID: <717@brchh104.bnr.ca>
Date: 8 Dec 90 22:07:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sun-Spots
Lines: 22
Approved: Sun-Spots@rice.edu
X-Original-Date: Thu, 06 Dec 90 11:02:14 EST
X-Sun-Spots-Digest: Volume 9, Issue 397, message 9
X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu

It seems to me that there is a bug in the default root crontab that Sun
distributes with each machine such that it ends up causing a lot of
unnecessary NFS traffic each night.

Each of my SunOS 4.0.3 and SunOS 4.1 systems came with a line in root's
crontab which looks like this:

15 3 * * * find / -name .nfs\* -mtime +7 -exec rm -f {} \; -o -fstype nfs -prune

It seems as if the intent of the "-fstype nfs -prune" is to stop the find
from continuing onto remote systems.  However, if you try it you will see
that that clause only works if it comes before the rest of the find
statement.  If you change it to look like this it will work as intended:

15 3 * * * find / -fstype nfs -prune -o -name .nfs\* -mtime +7 -exec rm -f {} \;

I discovered the problem when there were problems with a subdirectory on a
remote host each of my suns sent me mail saying that they couldn't "find"
in that directory.

                --Jim Dempsey--
		jjd@bbn.com