- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: How to identify any processes running on a hug...
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО03-04-2011 05:01 AM
тАО03-04-2011 05:01 AM
Re: How to identify any processes running on a huge directory structure?
for X in $LIST
do
unset running
running=`fuser $X 2>>/dev/null`
if [ -n "${running}" ] ; then
print X is $X and has pids of $running
# I can even take it a down a level
for P in $running
do
ps -fp $P
done
echo "------------------------\n"
fi
done
I used this. With it, I discovered a dynamic shared object of perl was running with apache on 3 development websites. I stopped the 3 and whammo. No use anymore.
I've never used lsof before. If I did, I probably would replace the fuser command with it.
This script would be a performance hog. I would not not want to run it on a whim.
But I minimized the affect by just looking at files ending .sl. I could see from my first accident, (ahem), that these were the only ones in use.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2011 06:16 AM
тАО03-04-2011 06:16 AM
SolutionIf you backup this directory with a utility that restores the lastaccesstime stamp of the files backed up, then consider using 'find' to see what has been accessed since some point in time.
For that matter, you still might glean some useful information if, for example, your complete backups were done weekly.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2011 06:23 AM
тАО03-04-2011 06:23 AM
Re: How to identify any processes running on a huge directory structure?
cd /A
find perl -atime -1 -type f -print
if something shows up, I know it's in use?
Or
find perl -atime +600 -type f -print >old
find perl -type f -print > all
diff old all | more
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2011 06:35 AM
тАО03-04-2011 06:35 AM
Re: How to identify any processes running on a huge directory structure?
> # find perl -atime -1 -type f -print
> if something shows up, I know it's in use?
Well, you know that it *has been* *accessed* (read or executed) not necessarily that it is in-use.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2011 07:24 AM
тАО03-05-2011 07:24 AM
Re: How to identify any processes running on a huge directory structure?
You can touch a reference file of an hour or so ago and then find files:
-neweram ref-file
- « Previous
-
- 1
- 2
- Next »