03-10-2013
Both your solutions will do the job. You didn't print as requested in 2.6, and you didn't mention the jobs' statuses. What status would you expect them in?
Use kill -9 only as a last resort for otherwise unaccessible processes. Usually, the default 15 (TERM) is sufficient. And, you can list several processs to kill in one command.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I was wondering if anyone has used VMWare Workstation? I wanted to practice and learn Unix in a networking environment and have my own home lab. However room and money prevent me from buying several computers to do so. Any input would help thank you. (0 Replies)
Discussion started by: vedder191
0 Replies
2. Programming
In the following Shell Script can anyone help me?
What are the total scripts?
What are the total binaries?
What are the total files?
#!/bin/sh
GREP="/bin/grep -q"
if ; then
if ; then
for | in ${I}/* ;do
file ${I} | ${GREP} "executable" && echo "${I} is a binary"
file ${I} |... (1 Reply)
Discussion started by: rktompsett
1 Replies
3. Shell Programming and Scripting
heres the lab i did everything but when i issue the automated lab check.
but it gives me this everytime
''you are missing the /home/smichaels/Labs/lab2b/group file, please create it as per step 12 of the lab.
once you have corrected this problem, re-run the uli101.023 program''
im... (1 Reply)
Discussion started by: ink
1 Replies
4. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
''you are missing the /home/smichaels/Labs/lab2b/group file, please create it as per step 12 of the lab.
once... (4 Replies)
Discussion started by: ink
4 Replies
5. Homework & Coursework Questions
hi.. this is shell scripting lab15.sh
i dont understand this lab i am at the screen shot part. i was wondering if someone can take a quick look at this lab i have linked the doc below. i dont know where to start
i have did the
Required Errorlevels
Errorlevel # but dont... (1 Reply)
Discussion started by: beerpong1
1 Replies
6. Shell Programming and Scripting
Write a script that copies the file tree (including subdirectories) in your home directory. As the initial directory to take the directory / usr / share / doc, as the destination directory using the directory $ {HOME} / doc.
Write a script corresponding to paragraph 1. Additional conditions: a)... (1 Reply)
Discussion started by: elginmulizwa
1 Replies
7. Hardware
So, I have a kindof off the wall question. I've got 10 computers which I inherited from a charter school that closed that I did their admin work for. They're not servers, just workstations with ubuntu server running on them. I had them all up and running at one point... but crimineys the load on my... (8 Replies)
Discussion started by: jtollefson
8 Replies
8. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Filter a file for lines that have exactly 5 numbers in a row.
2. Relevant commands, code, scripts,... (13 Replies)
Discussion started by: herb bertz
13 Replies
9. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Create a group id with your last name. Create 2 user IDs using your last name and the numbers 1 and 2. For each... (3 Replies)
Discussion started by: Jagst3r21
3 Replies
10. Hardware
Hello,
Do you have any suggestion of any tool (web based preferably) about how to organize a lab environment?
Now i save some info in excel sheet (one rack per column) , but i was thinking if any software exists.
Thanks in advance! (2 Replies)
Discussion started by: @dagio
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