(1) Replace "print `blahblah`" with "blahblah", the backtick (`) is really only useful for storing outputs in variables and using them embedded in other commandlines, if you just want to print the result direct to the screen and nothing else, you don't need them.
eg
(2) You could use killall to do what you want here but I dislike it as it can do horribly wrong on you if you are not careful.
Note that if the user puts something silly (like "a" for example) in the THINGIWANTOSEARCHFOR variable, many many many pids can end up in the resultant list.
I searched the post and someone said to clear the screen in C, use
printf("\033[2J"); ??
However, this doesn't work...typo or no.
What is an equivalent command to 'CLS' in DOS/'clear' in UNIX to clear the screen and go to top of screen??
Thank you. (2 Replies)
HPUX 11.0.X / Korn Shell
Hope this makes sense.
I have a little function to place things on the screen using the column and row parameters. Question is, how can I be sure of where the current cursor postion is so that if I print something to the upper right hand corner of the screen, I can... (2 Replies)
Hi
There is a program running which displays output on the screen
I have to grep a particular string from that screen how do i do this
My problem is i'm running this program from a script which executes after every fifteen mins but sometimes it's happen that there is an error in the program... (4 Replies)
I'm using Fedora3 and Screen
when i do that, Scree dont load my Bash profile
so my MC, centericq and swedish keyboard is mesed up..
how can i use screen and my bash_profile?
or is there another way to fix it? (0 Replies)
Hi Guys,
I'm using a double screen machine with linux Red Hat. The problem is that I see the same image in both screens...
Can anybody tell me how to solve this problem?
Thanks a lot,
Pablo. (0 Replies)
Hello everyone!
I'm trying to figure out how to send commands from one screen to another.
For example i wish to send a simple "ls -all" from screen #1 to screen #2,
can it be done, and how? :confused:
Thank you! (12 Replies)
Hi,
I'm trying to create a virtual screen, (maybe xvfb? or any other virtual screen buffer) and be able to use Screen Sharing to connect to it.
The setup is that I have a Mac Mini connected to the TV. But when my girlfriend is using Front Row, I can't use Screen Sharing at the same time from... (0 Replies)
I am using Intel HD 400 Graphics on a laptop.
When I logout, I get a black screen with no cursor or anything. I have to hard reboot the system to get into linux again.
Working on RHEL 6 (gnome) (1 Reply)
I made a screen within a screen.
Is there a way to move the inner screen up one level so that it is at the same level as the first screen running from the shell? (2 Replies)
Discussion started by: phpchick
2 Replies
LEARN ABOUT REDHAT
killall
KILLALL(1) User Commands KILLALL(1)NAME
killall - kill processes by name
SYNOPSIS
killall [-e,--exact] [-g,--process-group] [-i,--interactive] [-q,--quiet] [-v,--verbose] [-w,--wait] [-V,--version] [-S,--sid] [-c,--con-
text] [-s,--signal signal] [--] name ...
killall -l
killall -V,--version
DESCRIPTION
killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent.
Signals can be specified either by name (e.g. -HUP) or by number (e.g. -1).
If the command name contains a slash (/), processes executing that particular file will be selected for killing, independent of their name.
killall returns a zero return code if at least one process has been killed for each ilisted command. killall returns zero otherwise.
A killall process never kills itself (but may kill other killall processes).
OPTIONS -e, --exact
Require an exact match for very long names. If a command name is longer than 15 characters, the full name may be unavailable (i.e.
it is swapped out). In this case, killall will kill everything that matches within the first 15 characters. With -e, such entries
are skipped. killall prints a message for each skipped entry if -v is specified in addition to -e,
-g, --process-group
Kill the process group to which the process belongs. The kill signal is only sent once per group, even if multiple processes belong-
ing to the same process group were found.
-i, --interactive
Interactively ask for confirmation before killing.
-l, --list
List all known signal names.
-q, --quiet
Do not complain if no processes were killed.
-v, --verbose
Report if the signal was successfully sent.
-V, --version
Display version information.
-w, --wait
Wait for all killed processes to die. killall checks once per second if any of the killed processes still exist and only returns if
none are left. Note that killall may wait forever if the signal was ignored, had no effect, or if the process stays in zombie
state.
-S (Flask only) Specify SID: kill only processes with given SID. Mutually exclusive with -c argument. Must precede other arguments on
command line.
-c (Flask only) Specify security context: kill only processes with given security context. Mutually exclusive with -s. Must precede
other arguments on the command line.
FILES
/proc location of the proc file system
KNOWN BUGS
Killing by file only works for executables that are kept open during execution, i.e. impure executables can't be killed this way.
Be warned that typing killall name may not have the desired effect on non-Linux systems, especially when done by a privileged user.
killall -w doesn't detect if a process disappears and is replaced by a new process with the same PID between scans.
AUTHORS
Werner Almesberger <Werner.Almesberger@epfl.ch> wrote the original version of psmisc. Since version 20 Craig Small <csmall@small.drop-
bear.id.au> can be blamed.
SEE ALSO kill(1), fuser(1), pgrep(1), pidof(1), ps(1), kill(2)Linux March 25, 2001 KILLALL(1)