- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Problems with find command
Operating System - HP-UX
1748283
Members
3703
Online
108761
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2009 02:53 AM
тАО02-24-2009 02:53 AM
Problems with find command
Experiencing some strange behaviour when running find commands on an RX2660, HP-UX 11.31
As soon as the find command is initiated, e.g. 'find / -name cache.cpf'
there is what seems like a massive perfomance hit. Any new logons just hang around, and won't respond until the find command is killed off, which in itself takes some time.
We don't have this problem on our old D-class servers, so I'm surprised that there appears to be a problem on the newer hardware.
Is there a known problem with this command?
As soon as the find command is initiated, e.g. 'find / -name cache.cpf'
there is what seems like a massive perfomance hit. Any new logons just hang around, and won't respond until the find command is killed off, which in itself takes some time.
We don't have this problem on our old D-class servers, so I'm surprised that there appears to be a problem on the newer hardware.
Is there a known problem with this command?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2009 03:02 AM
тАО02-24-2009 03:02 AM
Re: Problems with find command
Hi:
> Is there a known problem with this command?
Well, yes, insofar as you are causing 'find' to search _every_ directory on your server. If you have a large number of directories and files therein then this is going to take quite a while. You should restrict your search to one or more "logical" places; for instance:
# find /opt /cachedb -xdev -type f -name cache.cpf
The addition of '-xdev' prevents crossing mountpoints and '-f' limits matches to files.
If you have a DVD or CD mounted or an NFS mount you may also see slower response. Another way to eliminate searching these mountpoints is to limit 'find()' to a specific filesystem type, for example:
# find /opt /cachedb -fsonly JFS ...
See the 'find' manpages for more information.
Regards!
...JRF...
> Is there a known problem with this command?
Well, yes, insofar as you are causing 'find' to search _every_ directory on your server. If you have a large number of directories and files therein then this is going to take quite a while. You should restrict your search to one or more "logical" places; for instance:
# find /opt /cachedb -xdev -type f -name cache.cpf
The addition of '-xdev' prevents crossing mountpoints and '-f' limits matches to files.
If you have a DVD or CD mounted or an NFS mount you may also see slower response. Another way to eliminate searching these mountpoints is to limit 'find()' to a specific filesystem type, for example:
# find /opt /cachedb -fsonly JFS ...
See the 'find' manpages for more information.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2009 03:09 AM
тАО02-24-2009 03:09 AM
Re: Problems with find command
I appreciate it's not the most efficient way to run the command, searching root, but as I mentioned, it's never had this sort of impact before.
Will take your advice on board though, thanks.
Will take your advice on board though, thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2009 03:22 AM
тАО02-24-2009 03:22 AM
Re: Problems with find command
Does your old D class run the same hpux version.
the command you run is very intensive, searching from root.
there were some inconsistencies with the find command, please check this patch PHCO_36666,worth updating if not present already.
the command you run is very intensive, searching from root.
there were some inconsistencies with the find command, please check this patch PHCO_36666,worth updating if not present already.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP