Take the 2-minute tour ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.

Is there a way to generate a full process listing in solaris, without truncated lines? I've tried the ps command, with the following arguments:

  -f                  Generates a full listing. (See below for
                      significance  of columns in a full list-
                      ing.)
  -l                  Generates a long listing. (See below.)

So, those both seem to do what I want, however, further down in the ps man page, I find this:

 
 args                    The command with all its arguments as  a
                         string.  The implementation may truncate
                         this value to the  field  width;  it  is
                         implementation-dependent   whether   any
                         further   truncation   occurs.   It   is
                         unspecified     whether    the    string
                         represented is a version of the argument
                         list  as  it  was  passed to the command
                         when it started, or is a version of  the
                         arguments as they may have been modified
                         by the application. Applications  cannot
                         depend  on  being  able  to modify their
                         argument list and having that  modifica-
                         tion  be  reflected in the output of ps.
                         The Solaris  implementation  limits  the
                         string  to  80  bytes; the string is the
                         version of the argument list as  it  was
                         passed to the command when it started.

Which basically says the output is going to be truncated and there is nothing I can do about it. So, I'm coming here. Surely other people have run into this problem and maybe even have a way around it. I'm guessing ps can't do it and so I need to use other tools to do this. Is that accurate?

share|improve this question
    
Are you talking about the ps command? If so then please update the question so that it's clearer. –  phunehehe Nov 12 '10 at 17:31
    
Yeah, sorry... my initial tinkering was with the ps command, I've made the question clearer. –  gabe. Nov 13 '10 at 0:42

4 Answers 4

up vote 31 down vote accepted

you could try

pargs <PID>

this gives you a list of all arguments

or else use an other ps. If run as root (or any user with enough privileges for that matter)

/usr/ucb/ps auxww

will give you all arguments. Its part of SUNWscpu, "Source Compatibility, (Usr)"

share|improve this answer
    
pargs shows the in-process copy of the command line arguments (and optionally the environment). Good to know, thanks! –  Gilles Nov 11 '10 at 20:12
    
This works very nicely, thanks! –  gabe. Nov 16 '10 at 19:06
1  
this whole /usr/ucb directory is new to me... I like it! –  gabe. Nov 16 '10 at 20:39
1  
On Solaris 11, if you use options without a dash (like "/usr/bin/ps auxwww") they will be treated as UCB style options, and the output will show extra long lines, even when you are NOT running as root. This is not well publicized. See also: superuser.com/questions/148271/ps-command-in-solaris –  Chris Quenelle Nov 3 '12 at 4:22

The kernel is not required to keep track of command line arguments. When a program is started through the execve call, the kernel must copy the arguments into the process memory (so that they will be available as argv in a C program, for example). After that, the kernel can discard the memory used to store the initial command line arguments. The process is allowed to overwrite its copy of the arguments. So there may simply be no trace of the arguments.

Some unix variants do keep a copy of the arguments in some form. Solaris exposes some data in /proc/$pid. As of OpenSolaris 2009.06, the only trace of the arguments is in /proc/$pid/psinfo, where they are concatenated with spaces in between (so you can't distinguish between foo "one" "two" and foo "one two") and the resulting string is truncated to 80 bytes. This field in /proc/$pid/psinfo is what ps prints in the args column.

By the way, the -f and -l options control what fields are printed, not whether the fields are truncated to some width.

share|improve this answer
    
This was a good answer as well, very informative. The pargs command met my need better which is the only reason I selected that answer over this one. –  gabe. Nov 16 '10 at 19:07
3  
So, once again we sit here in year 2013 and still we truncate strings to 80 bytes because we only had 80-char terminals in the 1970s and "some" programs have yet to understand the fact that life has moved on. And we like it, we praise this as "compatibility"! We should be ashamed of ourselves... –  Manjabes Jan 3 '13 at 14:31

prstat will give you the currently running processes along with their pids and the CPU utilization.

share|improve this answer

Depending which ps command you use, I use

ps -auxw
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.