Ps command different behaviour

 
Thread Tools Search this Thread
Operating Systems Linux Red Hat Ps command different behaviour
# 8  
Old 09-12-2016
Quote:
Originally Posted by Albert_Pinto7
Hi Corona, it worked but not fully, if we pipe the output of this ps command to another command, such as grep, the grep wont get the full output of ps command which it would have got if COLUMNS var would not be set to our value

My regards,
Albert
You could alias ps into ps --cols ...
# 9  
Old 10-28-2016
Even if we set COLUMNS=50 and then export it, any user can come around this restriction using ps -ww
Also, in unix, by default the output of ps command is curtailed to I think 70 chars and that does not go away even if you use ps -ww. But unix provides full output to the user who actually ran that particular command. Its just that other users can only see the curtailed output.
e.g if an user say albert ran a program having a long param chain. If albert himself runs ps command, he can see the full length of his command under ps list, but say another user jim runs the ps command, he can only see the curtailed output of the command (which albert had put to run). Even -ww option used by jim wont enable him to get the full command output.
Having said this, jim can see full output(more than 70 chars) of his programs under ps output list.
# 10  
Old 11-04-2016
Are you attempting to stop other users from seeing sensitive things in ps listings? If so, curtailing ps won't stop them, there are other ways to obtain the commandline of a process.
# 11  
Old 11-04-2016
Yes I agree, but the same stuff was smartly handled in Solarix, in which, they had truncated the output to 80 chrs. Thus all the sensitive info was cut off. So was wondering if that can be done in Linux.
Also, the use of columns env variable can not be a fool prof solution as its value can be changed. Even if we make it a readonly, its value can be changed in child processes and the readonly attribute does not hold true there.
# 12  
Old 11-07-2016
Short answer: No.

Long answer: Obscurity is not security. ps is not a security tool. Even if you convinced ps to block the information, users could just get it direct from the source in /proc/####/comm.

Do you know for a fact that the first 80 chars never contains sensitive information, anyway? Commandline arguments were never a particularly safe place to put such things.
# 13  
Old 11-07-2016
Quote:
the same stuff was smartly handled in Solarix, in which, they had truncated the output to 80 chrs.
Funny on my solaris system with 130 char width and typing
Code:
 ps -ef |more

I have lines going to the end...
# 14  
Old 11-07-2016
Even if it is so, if I get to truncate the ps command output to 80 chars for everyone(apart from process owner and root) then I will reach the goal.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Behaviour of pwd command in sh and ksh

I have a script as below. bash-3.00$ cat test.sh #!/usr/bin/ksh path=`pwd` echo $path var=$path/temp11 echo $var If run it is giving output bash-3.00$ ksh test.sh //var/tmp/SB2/miscellaneous //var/tmp/SB2/miscellaneous/temp11 (5 Replies)
Discussion started by: millan
5 Replies

2. Shell Programming and Scripting

Exec command behaviour

Hello All, I came across this line in a shell script that I was looking at yesterday. Couldn't get a clue of what it does. :confused: .... .... blah blah .... ..... exec >&- 2>&- ...... blah blah ..... Can someone explain me this?? Usually I have seen exec commands used to... (3 Replies)
Discussion started by: PikK45
3 Replies

3. UNIX for Dummies Questions & Answers

Behaviour of "find" command

Hi, I'm trying to understand why the find command below is not listing a directory which was modified long back from the number of days specified in the mtime part. :confused: user-aster :/mydir $ ls -ld 1607570a-4fed44bb-4988 drwxr-xr-x 3 xyz abc 4096 Jun 29 01:02 1607570a-4fed44bb-4988... (4 Replies)
Discussion started by: aster007
4 Replies

4. Programming

different behaviour in fg and bg

fg = foreground bg = background I have a cobol program that I start with a very simple script. The script is not at fault as it has not changed and the program worked in fg and bg before. I have altered the logging in the program and moved my cursor declare to working storage. The program runs... (6 Replies)
Discussion started by: Bruble
6 Replies

5. Shell Programming and Scripting

Strange "cut" command's behaviour

Hi, Suppose if I have a file having data like this: $ cat file.txt A B C D And, if I do a cut operation like this: $ cut -d" " -f2 file.txt The output is A C D This is the same for even if we try to get the field 3 with -f3 (assume line 2 has 3 fields : C E F). The above... (1 Reply)
Discussion started by: royalibrahim
1 Replies

6. Shell Programming and Scripting

unix "trap" command behaviour

Hi I am using "trap" command in my script to prevent the user from running Ctrl-C during the its execution. My script creates number of children processes which in turn create some children processes as well during the execution. When user / tester tries to run Ctrl-C, the parent process is... (1 Reply)
Discussion started by: aoussenko
1 Replies

7. Shell Programming and Scripting

cp -R behaviour

i 've noticed the following difference between freebsd cp and gnu cp from the freebsd cp man page: -R ... If the source_file ends in a /, the contents of the directory are copied rather than the directory itself. ... on gnu cp from the man pagewhile on gnu cp manpage: ‘-r'... (2 Replies)
Discussion started by: aegis
2 Replies

8. Shell Programming and Scripting

Why this behaviour of IF condition?

I have a variable, defndata, which is a number (fetched from a file using awk). I want that if defndata is not initialized (that is its not found in the file using awk), then to execute a block of statements, otherwise execute another block. if then .... else ... fi Now this... (4 Replies)
Discussion started by: indianjassi
4 Replies

9. UNIX for Advanced & Expert Users

Sort command - strange behaviour

Hi guys, I have the following example data: A;00:00:19 B;00:01:02 C;00:00:13 D;00:00:16 E;00:02:27 F;00:00:12 G;00:00:21 H;00:00:19 I;00:00:13 J;00:13:22 I run the following sort against it, yet the output is as follows: sort -t";" +1 -nr example_data.dat A;00:00:19 (16 Replies)
Discussion started by: miwinter
16 Replies

10. Shell Programming and Scripting

Help me to resolve uncertian behaviour of a sort command

I have got a file BeforeSort.txt having 40 fields seperated by "|" First field= RecordType (Value will be P or FP) Second field= CamCode Third field = UpdatingDate Fourth field = ProductType Fifth field = ActionCode (Value may be 01, 02 or 03) Sixth field = ProductCode and so on My... (1 Reply)
Discussion started by: pankajrai
1 Replies
Login or Register to Ask a Question