I am struggling with the proper usage of the NIX "find" command on a
Foxboro mangled (uh, make that integrated), Sun system.
here's the scenario, I am running 6.1, which translates to Sun-OS 2.5.1.
Foxboro seems to have mounted some of the remote machines under the /rem
hierarchy. If I type, for instance, "find / -name core -print". I get
a huge number of complaints about things in this /rem hierarchy which
don't exist. I suspect that this is because of symlinks on the remote
machines which don't point to valid places, when viewed from this
hierarchy.
What I really want to do, is limit find's search to local file-systems
only.
Now here is where it gets event stranger. I called Foxboro support to
ask about this, and was told to use the following syntax:
find / -fstype urfs -o name core -print.
First, as far as I can determine "urfs" is not a valid file-system type.
ufs, of course is, but the support person was adamant about urfs being
correct. Second the -o (or) flag does not make sense here. What I think
should be used here is an _and_, that is both conditions should be met
before printing the filename. And is the default behavior here.
Anyone have any clues here? And while I posting, what magic does
Foxboro use to mount the /rem hierarchy? I would have used the
automounter here, so that the remote machines are only mounted when I
need them. This would have avoided this whole problem. Are they hard
mounting the remote machines? I seem to have only some, not all, of my
remote machines mounted on a given cluster (node).
Thanks for any help on this.
--
Stan Brown [EMAIL PROTECTED] 843-745-3154
Charleston SC.
--
Windows 98: n.
useless extension to a minor patch release for 32-bit extensions and
a graphical shell for a 16-bit patch to an 8-bit operating system
originally coded for a 4-bit microprocessor, written by a 2-bit
company that can't stand for 1 bit of competition.
-
(c) 2000 Stan Brown. Redistribution via the Microsoft Network is prohibited.
-----------------------------------------------------------------------
This list is neither sponsored nor endorsed by the Foxboro Company. All
postings from this list are the work of list subscribers and no warranty
is made or implied as to the accuracy of any information disseminated
through this medium. By subscribing to this list you agree to hold the
list sponsor(s) blameless for any and all mishaps which might occur due to
your application of information received from this mailing list.
To be removed from this list, send mail to
[EMAIL PROTECTED]
with "unsubscribe foxboro" in the Subject. Or, send any mail to
[EMAIL PROTECTED]
