Sponsored Content
Top Forums UNIX for Beginners Questions & Answers Not really looking to replace ps, but is there a ps 'alternative'/wrapper tool Post 303031463 by bakunin on Friday 1st of March 2019 12:24:48 AM
Old 03-01-2019
Quote:
Originally Posted by newbie_01
I am looking for one that can maybe do the following:
  1. sort the process from oldest/newest running process
  2. list process that has been started x-time ago, i.e. x-hours/minutes ago. Most especially need this one
  3. list process 'complete' arguments
All this is relatively easy: ps has a lot of fields you can selectively display in the output. For instance:

"list process 'complete' arguments"

Start with ps -Ao. The -o takes a list of parameters, separated by comma, which are listed in the manpage. What you want here is (quotes from the Linux man page):

Code:
       -o format
              User-defined format.  format is a single argument in the form of
              a blank-separated or comma-separated list,

[...]

       args        COMMAND   command with all its arguments as a string.
                             Modifications to the arguments may be shown.  The
                             output in this column may contain spaces.[...]

So your command would be ps -Ao args to display the complete comands with arguments or maybe ps -Ao pid,ppid,args to display 3 columns with the process' ID, the parent PID and the complete command with arguments for each process, etc.. Analogous for your other requirements. Simply consult the man page and look up the "standard format specifiers" and which information they display.

You tailor the output using this the way you need it for your purposes. Then you do the sorting either by using the --sort parameter (again, see the man page for details) if you have the GNU-ps (which is not portable, so be warned) or just use the standard sort utility to sort ps's output.

I hope this helps.

bakunin
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Tcp wrapper

I installed tcp wrappers version 7.6 and modify my inetd.conf file from ftp stream tcp6 nowait root /usr/sbin/in.ftpd in.ftpd to ftp stream tcp6 nowait root /usr/local/bin/tcpd /usr/sbin/in.ftpd -l created /etc/hosts.allow file and modify it... (19 Replies)
Discussion started by: hassan2
19 Replies

2. UNIX for Dummies Questions & Answers

What is wrapper script and how to write

hi guys, I have a requirement to run a script 4 times with different parameter values. the 4 jobs have to run parallely which actually access different data of same table and deletes. how can i achieve this.................? Thanks in advance (1 Reply)
Discussion started by: chiru
1 Replies

3. Shell Programming and Scripting

wrapper for Common Tools

Hi All, I have bunch of different versions of generic tools (like gcc, gdb, ddd etc) and these tools are compiled for different platforms (linux, solaris...) I would like to mount all these tools into some common place (like /nfs/tools/bin) and have the wrapper to pull the latest version of the... (2 Replies)
Discussion started by: cantgetname
2 Replies

4. UNIX for Dummies Questions & Answers

What is a wrapper script

I tried searching the forum ,,but couldn't locate ..Can anyone give me a link or some information about wrapper script. (1 Reply)
Discussion started by: thana
1 Replies

5. UNIX for Dummies Questions & Answers

Writing a wrapper

Hi everyone, I have this custom sudo package over which I want to write a wrapper using PERL. The wrapper will do some pre-work and then call the regular sudo package from within itself. But I am facing a peculiar problem here. Once invoked, I am able to do the pre-work from within the... (1 Reply)
Discussion started by: garric
1 Replies

6. Shell Programming and Scripting

Help with a wrapper script not working

Hello, I have the below wrapper script: #!/usr/bin/perl -w if ($^O eq 'MSWin32' ) { $subnet = 'c:\path\to\subnet.txt'; } else { $subnet = '/opt/qip/wrapper-del-sub'; } open FH1, 'jj-deleted-subnets.txt' or die "Can't open 'jj-deleted-subnets.txt' ... (0 Replies)
Discussion started by: richsark
0 Replies

7. UNIX for Dummies Questions & Answers

SSH/SSL wrapper

My IRC client does not support SSL, so I was wondering if there was any other way to encrypt the information between SSL clients on an IRC network, maybe by using SSH to enter the IRC program or something (it's a command-line program) and passing all the plain-text through SSH first. I tried... (0 Replies)
Discussion started by: guitarscn
0 Replies

8. Solaris

Is alternative tool available just like SUDO?

Hello, GA. Do any one know any similar pkgs just like SUDO for solaris. Ultimate thing is, I need to grand root access for my normal account (xyz). 1) Without providing UID 0 for xyz 2) SUDO pkg is not allowed to install Could someone please tell me, if any other alternative tool... (7 Replies)
Discussion started by: bullz26
7 Replies

9. UNIX for Dummies Questions & Answers

What is a wrapper?

Hi, I am a dummy and hear to the computation guys telling me, "Oh! that is easy, you just write a wrapper to do all that bunch of stuff!" :cool: Could someone tell me what is a wrapper? :rolleyes: The only one I know is Cling-Wrap for sandwiches. A small elegant example would be very... (1 Reply)
Discussion started by: genehunter
1 Replies

10. Shell Programming and Scripting

Need wrapper around mysql query

Hello Friends, I am using check_mysql_query plugin in nagios to query database and get output. query is working fine but output which i am getting contain query. I want to remove query from output and give custom message which will be simple and understandable. Can you help me here with any... (5 Replies)
Discussion started by: ghpradeep
5 Replies
PKILL(1)						    BSD General Commands Manual 						  PKILL(1)

NAME
pgrep, pkill -- find or signal processes by name SYNOPSIS
pgrep [-LSafilnoqvx] [-F pidfile] [-G gid] [-M core] [-N system] [-P ppid] [-U uid] [-c class] [-d delim] [-g pgrp] [-j jid] [-s sid] [-t tty] [-u euid] pattern ... pkill [-signal] [-ILafilnovx] [-F pidfile] [-G gid] [-M core] [-N system] [-P ppid] [-U uid] [-c class] [-g pgrp] [-j jid] [-s sid] [-t tty] [-u euid] pattern ... DESCRIPTION
The pgrep command searches the process table on the running system and prints the process IDs of all processes that match the criteria given on the command line. The pkill command searches the process table on the running system and signals all processes that match the criteria given on the command line. The following options are available: -F pidfile Restrict matches to a process whose PID is stored in the pidfile file. -G gid Restrict matches to processes with a real group ID in the comma-separated list gid. -I Request confirmation before attempting to signal each process. -L The pidfile file given for the -F option must be locked with the flock(2) syscall or created with pidfile(3). -M core Extract values associated with the name list from the specified core instead of the currently running system. -N system Extract the name list from the specified system instead of the default, which is the kernel image the system has booted from. -P ppid Restrict matches to processes with a parent process ID in the comma-separated list ppid. -S Search also in system processes (kernel threads). -U uid Restrict matches to processes with a real user ID in the comma-separated list uid. -d delim Specify a delimiter to be printed between each process ID. The default is a newline. This option can only be used with the pgrep command. -a Include process ancestors in the match list. By default, the current pgrep or pkill process and all of its ancestors are excluded (unless -v is used). -c class Restrict matches to processes running with specified login class class. -f Match against full argument lists. The default is to match against process names. -g pgrp Restrict matches to processes with a process group ID in the comma-separated list pgrp. The value zero is taken to mean the process group ID of the running pgrep or pkill command. -i Ignore case distinctions in both the process table and the supplied pattern. -j jid Restrict matches to processes inside jails with a jail ID in the comma-separated list jid. The value ``any'' matches processes in any jail. The value ``none'' matches processes not in jail. -l Long output. For pgrep, print the process name in addition to the process ID for each matching process. If used in conjunction with -f, print the process ID and the full argument list for each matching process. For pkill, display the kill command used for each process killed. -n Select only the newest (most recently started) of the matching processes. -o Select only the oldest (least recently started) of the matching processes. -q Do not write anything to standard output. -s sid Restrict matches to processes with a session ID in the comma-separated list sid. The value zero is taken to mean the session ID of the running pgrep or pkill command. -t tty Restrict matches to processes associated with a terminal in the comma-separated list tty. Terminal names may be of the form ttyxx or the shortened form xx. A single dash ('-') matches processes not associated with a terminal. -u euid Restrict matches to processes with an effective user ID in the comma-separated list euid. -v Reverse the sense of the matching; display processes that do not match the given criteria. -x Require an exact match of the process name, or argument list if -f is given. The default is to match any substring. -signal A non-negative decimal number or symbolic signal name specifying the signal to be sent instead of the default TERM. This option is valid only when given as the first argument to pkill. If any pattern operands are specified, they are used as regular expressions to match the command name or full argument list of each process. If the -f option is not specified, then the pattern will attempt to match the command name. However, presently FreeBSD will only keep track of the first 19 characters of the command name for each process. Attempts to match any characters after the first 19 of a command name will quietly fail. Note that a running pgrep or pkill process will never consider itself nor system processes (kernel threads) as a potential match. EXIT STATUS
The pgrep and pkill utilities return one of the following values upon exit: 0 One or more processes were matched. 1 No processes were matched. 2 Invalid options were specified on the command line. 3 An internal error occurred. COMPATIBILITY
Historically the option ``-j 0'' means any jail, although in other utilities such as ps(1) jail ID 0 has the opposite meaning, not in jail. Therefore ``-j 0'' is deprecated, and its use is discouraged in favor of ``-j any''. SEE ALSO
kill(1), killall(1), ps(1), flock(2), kill(2), sigaction(2), pidfile(3), re_format(7) HISTORY
The pkill and pgrep utilities first appeared in NetBSD 1.6. They are modelled after utilities of the same name that appeared in Sun Solaris 7. They made their first appearance in FreeBSD 5.3. AUTHORS
Andrew Doran <ad@NetBSD.org> BSD
August 9, 2013 BSD
All times are GMT -4. The time now is 03:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy