On Fri, Feb 15, 2002 at 09:26:49AM +0100, Ismael Touama wrote:
> > For example, a find command could set it off
>
> Don't understand what you can do with a "find" (not fine ?)
> command.
Let's say I'm trying to find a specific file that I'm pretty sure is
somewhere on the disk (something I do more than you might think). I
do something like
$ find / -iname "filename" 2>/dev/null
If I had autofs setup, when the find command accessed the directory
which is setup as a mount point for autofs to use, it would cause
autofs to attempt to mount the device. Chances are there wouldn't be
a medium in the drive, and I would have to wait for it to figure that
out. Plus, my floppy drive is currently broken. :) One could add
-path and -prune args to "find" in this case, but it gets a little
messy. I'd also have to exclude those dirs from my backup scripts
(not hard to do), and tell tripwire to ignore them. There are
probably some other things I haven't thought of, too.
None of those problems are all that big a deal, it's just that I
_very_ rarely use my floppy drive, and don't use the cdrom often
except for backups. So it's just a matter of what you think is best
for your situation. I just thought I'd expound on what I meant about
the "find" command. :)
Regards,
Ben
--
Ben Logan: ben at wblogan dot net
OpenPGP Key KeyID: A1ADD1F0
Hoffer's Discovery:
The grand act of a dying institution is to issue a newly
revised, enlarged edition of the policies and procedures manual.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
