If you're interested in the gory details, check out the proc(4) man page ("man -s4 proc"), specifically the psinfo and as files. psinfo contains two things to help you:
  1. The first 80 characters of the original command line, basically, the string that /usr/bin/ps prints.
  2. The address of the process's original argument list, within its address space. By opening the as file and seeking to this address, you can read the arg list out of the process's address space.
In principle, you could use perl to do either of these things. Hopefully you're familiar with pack and unpack.

In reply to Re: overcoming the 80 character limitation of solaris ps by kjherron
in thread overcoming the 80 character limitation of solaris ps by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.