It is
or better
Even better is to check for the elapsed time
The *-* matches anything with a dash; this is true if the process is more than one day old. So it will fix your emergency, but leave enough rpm processes running to remind you to do a root cause analysis plus a proper fix.
Hi everybody:
I have a problem. I have a output files which have this pattern:
number1
--space
block1a - 7rows/10columns/65elements
--space
block1b - 7rows/10columns/65elements
--space
block1c - 7rows/10columns/65elements
--space
number2
--space
block2a - 7rows/10columns/65elements... (0 Replies)
Hi, Im very new to the world of sed so I'm really not even sure if this is possible. What i need to do is read from a flat file and every time i see this line:
VAL=123,456
I need to change 456 to 457 for every occurence of this line in the file. The numbers 123 and 456 are different for... (6 Replies)
Hi All,
I am spooling the data some sql queries into a single file but wanted to know how to format the data of the file generated by spool.
#!/bin/sh
unset -f USAGE
USAGE () {
clear
echo "############################USAGE#######################\n"
echo "Incorrect number of... (2 Replies)
Hello,
I need help on how to "access" or manipulate the Linux ARP Cache in C, here is the description of the project i'm working in:
There are a lot of tools that analize ARP frames and send an e-mail to the sysadmin, that's easy. What i want to do is to inspect every ARP frame that arrives... (18 Replies)
Hi,
I am new to awk/unix and am trying to put together a script to manipulate the date column in a csv file.
I have file1.csv with the following contents:
Date,ID,Number,Amount,Volume,Size
01-Apr-2014,WERFG,998,105873.96,10873.96,1342.11
01-Apr-2014,POYFR,267,5681.44,5681.44,462.96
I... (2 Replies)
Hi, I am new to awk and unix programming and trying to manipulate a csv file.
My current csv file looks like this:
col1,col2,col3,col4,col5,col4,col5,col6,col7,col8
223,V,c,2,4,f,r,,y,z
223,V,c,3,2,f,r,,y,z
223,V,c,1,4,f,r,,y,z
223,V,c,4,3,f,r,,y,z
227,V,c,3,1,f,r,,y,z... (8 Replies)
Hello,
I am on a Mac and trying to clean up some monthly files with a very simple SED:
sed '3,10d;/<ACROSS>/,$d' input.txt > output.txt
(from the input, delete lines 3 - 10; then delete from the line containing <ACROSS> to the end of the file)
then output to output.txt
Even when I try... (2 Replies)
Discussion started by: verbatim
2 Replies
LEARN ABOUT OPENDARWIN
killall
KILLALL(1) BSD General Commands Manual KILLALL(1)NAME
killall -- kill processes by name
SYNOPSIS
killall [-d | -v] [-h | -?] [-help] [-l] [-m] [-s] [-u user] [-t tty] [-c procname] [-SIGNAL] [procname ...]
DESCRIPTION
Killall kills processes selected by name, as opposed to the selection by pid as done by kill(1). By default, it will send a TERM signal to
all processes with a real UID identical to the caller of killall that match the name procname. The super-user is allowed to kill any
process.
The options are as follows:
-d | -v Be more verbose about what will be done. For a single -d option, a list of the processes that will be sent the signal will
be printed, or a message indicating that no matching processes have been found.
-h | -?
-help Give a help on the command usage and exit.
-l List the names of the available signals and exit, like in kill(1).
-m Match the argument procname as a (case insensitive) regular expression against the names of processes found. CAUTION!
This is dangerous, a single dot will match any process running under the real UID of the caller.
-s Show only what would be done, but do not send any signal.
-SIGNAL Send a different signal instead of the default TERM. The signal may be specified either as a name (with or without a lead-
ing SIG), or numerically.
-u user Limit potentially matching processes to those belonging to the specified user.
-t tty Limit potentially matching processes to those running on the specified tty.
-c procname
When used with the -u or -t flags, limit potentially matching processes to those matching the specified progname.
ALL PROCESSES
Sending a signal to all processes with uid XYZ is already supported by kill(1). So use kill(1) for this job (e.g. $ kill -TERM -1 or as root
$ echo kill -TERM -1 | su -m <user>)
DIAGNOSTICS
The killall command will respond with a short usage message and exit with a status of 2 in case of a command error. A status of 1 will be
returned if either no matching process has been found or not all processes have been signalled successfully. Otherwise, a status of 0 will
be returned.
Diagnostic messages will only be printed if requested by -d options.
SEE ALSO kill(1), sysctl(3)HISTORY
The killall command appeared in FreeBSD 2.1. It has been modeled after the killall command as available on other platforms.
AUTHORS
The killall program was originally written in Perl and was contributed by Wolfram Schneider, this manual page has been written by Jorg
Wunsch. The current version of killall was rewritten in C by Peter Wemm using sysctl(3).
BSD June 25, 1995 BSD