<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Very long command line in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612553#M234680</link>
    <description>Maybe you need to change the strategy. Like, before launching the process, echo the PID and the command line with args to a directory, more or less the information that you would find in /proc in linux.&lt;BR /&gt;&lt;BR /&gt;Like:&lt;BR /&gt;&lt;BR /&gt;echo $$ &amp;gt; /process/run/process_name&lt;BR /&gt;very_large_command_line &amp;gt;&amp;gt; /process/run/proccess_name&lt;BR /&gt;rm /process/run/process_name</description>
    <pubDate>Thu, 20 Oct 2005 10:34:13 GMT</pubDate>
    <dc:creator>Ivan Ferreira</dc:creator>
    <dc:date>2005-10-20T10:34:13Z</dc:date>
    <item>
      <title>Very long command line</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612546#M234673</link>
      <description>One of the users at my site is running a command which is 1232 characters long, and wishes to view the complete commandline using ps. I know about the limit of 1024 bytes (used to be 64 bytes before 11i) of the command line that is stored in the kernel and about the ps -efx that shows up to 1024 characters of the command.&lt;BR /&gt;&lt;BR /&gt;Is there any other way to view all of those 1232 characters of the command line? Maybe the arguments are stored in de process memory? And if they are, can I retrieve them from a running process?&lt;BR /&gt;&lt;BR /&gt;I am aware that the command is ridicilously long, but shortening it is not an option!&lt;BR /&gt;&lt;BR /&gt;Tnx in advance,&lt;BR /&gt;Rik</description>
      <pubDate>Fri, 26 Aug 2005 03:09:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612546#M234673</guid>
      <dc:creator>RikTytgat</dc:creator>
      <dc:date>2005-08-26T03:09:39Z</dc:date>
    </item>
    <item>
      <title>Re: Very long command line</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612547#M234674</link>
      <description>Hi,&lt;BR /&gt;Not sure if it is possible to do exact what you as for but, it is possible to echo the command to a log file. I belive the command is started from a script or something (not typed in manually).</description>
      <pubDate>Fri, 26 Aug 2005 03:17:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612547#M234674</guid>
      <dc:creator>Leif Halvarsson_2</dc:creator>
      <dc:date>2005-08-26T03:17:40Z</dc:date>
    </item>
    <item>
      <title>Re: Very long command line</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612548#M234675</link>
      <description>Leif,&lt;BR /&gt;&lt;BR /&gt;I know what you mean, but other than helping my user, it made me curious, and after searching for several hours without finding a clue, I hoped to find some hints at the forums.&lt;BR /&gt;&lt;BR /&gt;Thanks anyway.</description>
      <pubDate>Fri, 26 Aug 2005 03:24:39 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612548#M234675</guid>
      <dc:creator>RikTytgat</dc:creator>
      <dc:date>2005-08-26T03:24:39Z</dc:date>
    </item>
    <item>
      <title>Re: Very long command line</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612549#M234676</link>
      <description>If you set up history file then it is possible,&lt;BR /&gt;&lt;BR /&gt;set -o vi&lt;BR /&gt;export $HISTFILE=$HOME/.sh_history&lt;BR /&gt;export $HISTSIZE=2000&lt;BR /&gt;&lt;BR /&gt;Example&amp;gt;&lt;BR /&gt;# echo "hai" | sed 's/hai/bye/' | awk '{ print $1 }' | sed 's/bye/hai/' | awk '{ print $1 }' | sed 's/hai/bye/' | awk '{ print $1 }' | sed 's/bye/hai/' | awk '{ print $1 }' | sed 's/hai/bye/' | awk '{ print $1 }' | sed 's/bye/hai/' | awk '{ print $0 }'&lt;BR /&gt;# history -2&lt;BR /&gt;2459    echo "hai" | sed 's/hai/bye/' | awk '{ print $1 }' | sed 's/bye/hai/' | awk '{ print $1 }' | sed 's/hai/bye/' | awk '{ print $1 }' | sed 's/bye/hai/' | awk '{ print $1 }' | sed 's/hai/bye/' | awk '{ print $1 }' | sed 's/bye/hai/' | awk '{ print $1 }'&lt;BR /&gt;&lt;BR /&gt;hth.</description>
      <pubDate>Fri, 26 Aug 2005 03:28:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612549#M234676</guid>
      <dc:creator>Muthukumar_5</dc:creator>
      <dc:date>2005-08-26T03:28:13Z</dc:date>
    </item>
    <item>
      <title>Re: Very long command line</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612550#M234677</link>
      <description>You are right, but my user needs to see the command line of the running process.</description>
      <pubDate>Fri, 26 Aug 2005 03:46:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612550#M234677</guid>
      <dc:creator>RikTytgat</dc:creator>
      <dc:date>2005-08-26T03:46:49Z</dc:date>
    </item>
    <item>
      <title>Re: Very long command line</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612551#M234678</link>
      <description>How about combining the above two:&lt;BR /&gt;&lt;BR /&gt;ps -ef | grep Pid_of_process | awk '{print NF}' | grep sh_history</description>
      <pubDate>Fri, 26 Aug 2005 04:23:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612551#M234678</guid>
      <dc:creator>Vibhor Kumar Agarwal</dc:creator>
      <dc:date>2005-08-26T04:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: Very long command line</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612552#M234679</link>
      <description>did you tried ps -efx ??</description>
      <pubDate>Thu, 20 Oct 2005 10:08:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612552#M234679</guid>
      <dc:creator>Calin Valentin</dc:creator>
      <dc:date>2005-10-20T10:08:14Z</dc:date>
    </item>
    <item>
      <title>Re: Very long command line</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612553#M234680</link>
      <description>Maybe you need to change the strategy. Like, before launching the process, echo the PID and the command line with args to a directory, more or less the information that you would find in /proc in linux.&lt;BR /&gt;&lt;BR /&gt;Like:&lt;BR /&gt;&lt;BR /&gt;echo $$ &amp;gt; /process/run/process_name&lt;BR /&gt;very_large_command_line &amp;gt;&amp;gt; /process/run/proccess_name&lt;BR /&gt;rm /process/run/process_name</description>
      <pubDate>Thu, 20 Oct 2005 10:34:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612553#M234680</guid>
      <dc:creator>Ivan Ferreira</dc:creator>
      <dc:date>2005-10-20T10:34:13Z</dc:date>
    </item>
    <item>
      <title>Re: Very long command line</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612554#M234681</link>
      <description>I am very curious to see a command that takes 1232 characters. Any chance you could share it?</description>
      <pubDate>Thu, 20 Oct 2005 13:21:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/very-long-command-line/m-p/3612554#M234681</guid>
      <dc:creator>Andy Torres</dc:creator>
      <dc:date>2005-10-20T13:21:43Z</dc:date>
    </item>
  </channel>
</rss>

