Path: utzoo!utgpu!cunews!bnrgate!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request
From: ssd@engr.ucf.edu (Steven S. Dick)
Newsgroups: comp.sys.sun
Subject: Re: root crontab bug? (Undocumented find -mount option)
Keywords: No Digest Subjects in Unmoderated Mode
Message-ID: <3131@brchh104.bnr.ca>
Date: 4 Jun 91 18:40:00 GMT
Sender: news@brchh104.bnr.ca
Organization: Sunspots, Psuedo-Unmoderated
Lines: 20
Approved: sun-spots@rice.edu
X-Original-Date:    Sun, 12 May 91 20:27:58 GMT

In article <2802@brchh104.bnr.ca> ray@kea.am.dsir.govt.nz (Ray Brownrigg) writes:
[stuff deleted]
>What is this leading up to? Well I believe that an undocumented option to
>find will alleviate the problem.
...
>The -mount option to find appears to restrict the activities of the
>command to the mounted partition(s) specified in the pathname-list. Thus
>the other common root crontab entry would be written something like:
>
>15 2 * * * find / /usr /home -mount -name core -atime +1 -exec rm {} \;
>
>The mount option seems to be commonly available - I first came across it
>on an AT&T 3B2 running SVR3.1!

This sounds an awful lot like the documented -xdev option.
Is there any difference?

	Steve
ssd@engr.ucf.edu