lsof equivalent on solaris

/usr/proc/bin/pfiles $PID
Report fstat(2) and fcntl(2) information for all open files in each process.

By: axelabs
2009-03-05 17:26:57

These Might Interest You

  • My old Solaris server does not have lsof, so I have to use pfiles.

    ps -ef | grep user | awk '{print $2}' | while read pid; do echo $pid ; pfiles $pid| grep portnum; done
    sharfah · 2010-01-11 12:34:51 1
  • Can use lsof, but since it's not part of the base OS, it's not always available. Show Sample Output

    for x in `ptree | awk '{print $1}'`; do pfiles $x | grep ${PORT} > /dev/null 2>&1; if [ x"$?" == "x0" ]; then ps -ef | grep $x | grep -v grep; fi; done 2> /dev/null
    bpfx · 2010-01-05 17:02:23 1
  • HP UX doesn't have a -a switch in the ifconfig command. This line emulates the same result shown in Solaris, AIX or Linux Show Sample Output

    for i in `netstat -rn |grep lan |cut -c55-60 |sort |uniq`; do ifconfig $i; done
    Kaio · 2010-01-28 17:35:20 2
  • This command is more portable than it's cousin netstat. It works well on all the BSDs, GNU/Linux, AIX and Mac OS X. You won't find lsof by default on Solaris or HPUX by default, but packages exist around the web for installation, if needed, and the command works as shown. This is the most portable command I can find that lists listening ports and their associated pid. Show Sample Output

    lsof -Pan -i tcp -i udp
    atoponce · 2010-06-07 15:22:44 0

What Others Think

Here is a good way to iterate through all processes: for PID in `/usr/bin/ps -e -o pid`;do echo Checking PID $PID... /usr/local/bin/sudo /usr/bin/pfiles $PID|grep port: done
axelabs · 364 weeks and 2 days ago
Sounds good, only one problem: NEVER do this on production system. The 'pfiles' command effectively halts the process in order to inspect it. (see the man page). If your process is doing heavy socket i/o while being halted it will crash as a result.
MrKnowItAll · 355 weeks ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: