Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!cornell!batcomputer!itsgw!steinmetz!uunet!convex!tchrist@convex.UUCP
From: tchrist@convex.UUCP (Tom Christiansen)
Newsgroups: comp.unix.wizards
Subject: Re: Using find(1) with obnoxious systems...
Message-ID: <658@convex.UUCP>
Date: 19 Oct 88 12:28:49 GMT
References: <2046@unmvax.unm.edu>
Sender: news@convex.UUCP
Reply-To: tchrist@convex.UUCP (Tom Christiansen)
Organization: CONVEX Technical Support Center, Richardson, TX
Lines: 20

In article <2046@unmvax.unm.edu> mike@turing.unm.edu (Michael I. Bushnell) writes:
>We have a number of systems.  They all mount user file systems using
>NFS.  The standard 4.3 /usr/adm/daily script does a nightly find on /,
>to clean '#' files, ',' files, 'core' files, and 'a.out' files.  We
>like this behavior.
>
>Is there a clever usage of -prune that would help, or are we hosed to
>using separate finds for each file system?

Certainly; for any find that you don't want to touch NFS file systems,
phrase it this way:
	find $dir \( -fstype nfs -prune \) -o ...
where ... is what you really wanted to do anyway.

--tom

    Tom Christiansen              {uiucdcs,ut-sally,sun}!convex!tchrist 
    Convex Computer Corporation                     tchrist@convex.COM
	UNIX Support, Training, and System Administration
	    "That's not a bug -- it's a feature!"