Very long command line

[RikTytgat]

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.

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?

I am aware that the command is ridicilously long, but shortening it is not an option!

Tnx in advance,
Rik

[Leif Halvarsson_2]

Hi,
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).

[RikTytgat]

Leif,

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.

Thanks anyway.

[Muthukumar_5]

If you set up history file then it is possible,

set -o vi
export $HISTFILE=$HOME/.sh_history
export $HISTSIZE=2000

Example>
# 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 }'
# history -2
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 }'

hth.

[RikTytgat]

You are right, but my user needs to see the command line of the running process.

[Vibhor Kumar Agarwal]

How about combining the above two:

ps -ef | grep Pid_of_process | awk '{print NF}' | grep sh_history

[Calin Valentin]

did you tried ps -efx ??

[Ivan Ferreira]

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.

Like:

echo $$ > /process/run/process_name
very_large_command_line >> /process/run/proccess_name
rm /process/run/process_name

[Andy Torres]

I am very curious to see a command that takes 1232 characters. Any chance you could share it?