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 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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
2. UNIX for Advanced & Expert Users
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
3. Shell Programming and Scripting
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
4. Shell Programming and Scripting
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
5. Shell Programming and Scripting
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
6. Shell Programming and Scripting
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
7. Programming
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
8. UNIX for Dummies Questions & Answers
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
9. Shell Programming and Scripting
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
10. Shell Programming and Scripting
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
PGREP(1) Linux User's Manual PGREP(1)
NAME
pgrep, pkill - look up or signal processes based on name and other attributes
SYNOPSIS
pgrep [-cflvx] [-d delimiter] [-n|-o] [-P ppid,...] [-g pgrp,...]
[-s sid,...] [-u euid,...] [-U uid,...] [-G gid,...]
[-t term,...] [pattern]
pkill [-signal] [-fvx] [-n|-o] [-P ppid,...] [-g pgrp,...]
[-s sid,...] [-u euid,...] [-U uid,...] [-G gid,...]
[-t term,...] [pattern]
DESCRIPTION
pgrep looks through the currently running processes and lists the process IDs which matches the selection criteria to stdout. All the cri-
teria have to match. For example,
pgrep -u root sshd
will only list the processes called sshd AND owned by root. On the other hand,
pgrep -u root,daemon
will list the processes owned by root OR daemon.
pkill will send the specified signal (by default SIGTERM) to each process instead of listing them on stdout.
OPTIONS
-c Suppress normal output; instead print a count of matching processes.
-d delimiter
Sets the string used to delimit each process ID in the output (by default a newline). (pgrep only.)
-f The pattern is normally only matched against the process name. When -f is set, the full command line is used.
-g pgrp,...
Only match processes in the process group IDs listed. Process group 0 is translated into pgrep's or pkill's own process group.
-G gid,...
Only match processes whose real group ID is listed. Either the numerical or symbolical value may be used.
-l List the process name as well as the process ID. (pgrep only.)
-n Select only the newest (most recently started) of the matching processes.
-o Select only the oldest (least recently started) of the matching processes.
-P ppid,...
Only match processes whose parent process ID is listed.
-s sid,...
Only match processes whose process session ID is listed. Session ID 0 is translated into pgrep's or pkill's own session ID.
-t term,...
Only match processes whose controlling terminal is listed. The terminal name should be specified without the "/dev/" prefix.
-u euid,...
Only match processes whose effective user ID is listed. Either the numerical or symbolical value may be used.
-U uid,...
Only match processes whose real user ID is listed. Either the numerical or symbolical value may be used.
-v Negates the matching.
-x Only match processes whose name (or command line if -f is specified) exactly match the pattern.
-signal
Defines the signal to send to each matched process. Either the numeric or the symbolic signal name can be used. (pkill only.)
OPERANDS
pattern
Specifies an Extended Regular Expression for matching against the process names or command lines.
EXAMPLES
Example 1: Find the process ID of the named daemon:
unix$ pgrep -u root named
Example 2: Make syslog reread its configuration file:
unix$ pkill -HUP syslogd
Example 3: Give detailed information on all xterm processes:
unix$ ps -fp $(pgrep -d, -x xterm)
Example 4: Make all netscape processes run nicer:
unix$ renice +4 `pgrep netscape`
EXIT STATUS
0 One or more processes matched the criteria.
1 No processes matched.
2 Syntax error in the command line.
3 Fatal error: out of memory etc.
NOTES
The process name used for matching is limited to the 15 characters present in the output of /proc/pid/stat. Use the -f option to match
against the complete command line, /proc/pid/cmdline.
The running pgrep or pkill process will never report itself as a match.
BUGS
The options -n and -o and -v can not be combined. Let me know if you need to do this.
Defunct processes are reported.
SEE ALSO
ps(1) regex(7) signal(7) killall(1) skill(1) kill(1) kill(2)
STANDARDS
pkill and pgrep were introduced in Sun's Solaris 7. This implementation is fully compatible.
AUTHOR
Kjetil Torgrim Homme <kjetilho@ifi.uio.no>
Albert Cahalan <albert@users.sf.net> is the current maintainer of the procps package.
Please send bug reports to <procps-feedback@lists.sf.net>
Linux June 25, 2000 PGREP(1)