Sponsored Content
Full Discussion: Kill Signal
Top Forums UNIX for Advanced & Expert Users Kill Signal Post 66140 by blowtorch on Thursday 10th of March 2005 10:41:08 PM
Old 03-10-2005
Read the rules buddy. No project related questions can be posted here.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

kill signal

Hello e'bdy, We have WebSphere MQ running on AIX 5.1 Every weekend MQ receives a kill -30 signal from some process or user and offloads a big error file. There is no way in MQ through which that process can be tracked. Is there something which i can do on UNIX level to trap the process? Best... (3 Replies)
Discussion started by: jhaavinash
3 Replies

2. UNIX for Advanced & Expert Users

When kill doesnt work, how to kill a process ?

Hi All, I am unable to kill a process using kill command. I am using HP-UX system. I have tried with kill -9 and i have root privilages. How can i terminate this daemon ? ? ? Regards, Vijay Hegde (3 Replies)
Discussion started by: VijayHegde
3 Replies

3. Programming

kill(0,-9) don't kill the process

Hi all i have simple c program , when i wish to kill the app im using kill(0,-9) , but it seams this command don't do any thing and the program. just ignore it . what im doing wrong here ? im using HP-UX ia64 Thanks (9 Replies)
Discussion started by: umen
9 Replies

4. UNIX for Advanced & Expert Users

Diff b/n kill and kill -9

Hi, I have a process with say pid x. What is the difference b/n kill x and kill -9 x in unix Thanks Ammu (2 Replies)
Discussion started by: ammu
2 Replies

5. Shell Programming and Scripting

Kill a process without using kill command

Sorry, posted the question in other forum. (0 Replies)
Discussion started by: sudhamacs
0 Replies

6. Linux

Kill a process without using kill command

I want to Kill a process without using kill command as i don't have privileges to kill the process. I know the pid and i am using Linux 2.6.9 OS. (6 Replies)
Discussion started by: sudhamacs
6 Replies

7. Shell Programming and Scripting

How to Trap kill -9 signal

I just want to trap kill -9 signal issued by any of user from any terminal and just capture that user terminal who had raised this kill -9 command (1 Reply)
Discussion started by: puneet.goel
1 Replies

8. UNIX for Dummies Questions & Answers

Meaning and typical use of -3 signal in kill

Hi, What is the use of the signal -3 in kill command in unix? I read the meaning and typical use of this signal in one of the Oreilly books as below. Quit -- stop running (and dump core). Sent when you type CTRL-\. what does the CTRL-\ command do? Is it the combination of CTRL and... (6 Replies)
Discussion started by: venkatesht
6 Replies

9. Solaris

Cannot kill a process with kill -9

Hello everyone, I have a process that I want to kill. I have tried kill-9 PID but it doesn't work. I have tried preap PID but it doesn't work too. The parent of my process is the process whose PID is 1, so I can't kill it. My OS is a Solaris 9. Can anyone help me understand what's going... (3 Replies)
Discussion started by: adilyos
3 Replies

10. Shell Programming and Scripting

Kill an specific process ID using the KILL and GREP commands

Good afternoon I need to KILL a process in a single command sentence, for example: kill -9 `ps -aef | grep 'CAL255.4ge' | grep -v grep | awk '{print $2}'` That sentence Kills the process ID corresponding to the program CAL255.4ge. However it is possible that the same program... (6 Replies)
Discussion started by: enriquegm82
6 Replies
wuzzah(1)							      Wuzzah?								 wuzzah(1)

NAME
wuzzah - keep an eye out for friends on a local system SYNOPSIS
wuzzah [OPTIONS...] DESCRIPTION
wuzzah is a program that just sits around and scans the utmpx entries to watch when your friends log in and out. By default upon invoca- tion, wuzzah looks for the file ${HOME}/.wuzzah, and loads the list of buddies contained therein (which are separated by newlines), and then sits and watches. If no file is found, and no other readable file is specified (see OPTIONS), wuzzah will attempt to just watch for whomever the current uid maps, and failing that will just quit. OPTIONS
-h, --help an informative usage summary, though nothing you don't see here... -a, --all-users watches for all users on the system, period. -c, --exec-cmd=CMD execute CMD upon a login. NOTE: this is done with a call to system(2), so you can do things like piping and whatever else you can do with sh -c -f, --buddy-file=FILE use FILE as buddyfile. naturally FILE must be readable, and consists of usernames, one to a line. optionally, these usernames can be followed by a colon, and then a wuzzah command-line to override wuzzah's behavior for this specific user. -F, --no-buddyfile tells wuzzah to not bother loading any config files. -i, --interval=NUM sleep NUM seconds between each polling -m, --message=STRING use STRING as a message template to greet logged-in buddies. See the section FORMATS for more information. -n, --no-newline don't end the messages with newlines (normally does by default) -o, --process-once scan the login records once, then exit -p, --process-current by default wuzzah doesn't message users who were already logged in when started up. this option overrides such behavior and mes- sages them anyways (only useful with the -w/-c options) -q, --silent don't message buddies when they log in (default). -s, --status-message=STRING use STRING as a template for displaying the status of people logging in and out. See FORMATS for more information. -u, --users=LIST adds every user in LIST (a space/comma/colon separated list of users) to the buddy list -v, --version the current version and copyright. -w, --write-buddies turns on messaging of buddies as they log in. NOTE: this can get quite annoying rather quickly. tune in soon for a less annoying solution FORMATS
message templates can be defined as normal character strings, interspersed with special format characters. format characters consist of a `%', followed by a character, which defines situation-specific data. The current list of these characters is as follows: a the alert character ('a') b the name of the buddy who has logged in/out d the date, currently in HH:MM:SS format h and H the remote hostname or IP address (respectively) of your buddy's login l the line in/out on which the buddy is logged (typically, something like /dev/pts/9 or /dev/ttyS0) m whether or not you have just messaged your buddy (really only useful for the -s option) n an embedded newline character o your buddy's online status ("logged on" or "logged off") u your own username, as can best be determined by the program. EXAMPLES
a simple invocation: username@machine$ wuzzah (13:45:39) foo logged in on :0 (not messaging). (13:45:39) bar logged in on pts/11 (not messaging). Message from username@machine on pts/11 at 14:00 ... (wuzzah) username says: "shoutout to my homie foo." EOF an example with a little more user customization: username@machine$ wuzzah --message="hey, %b, it's %u. nice to see you at %d!" and when foo logs in, foo will get a message like so: Message from username@machine on pts/11 at 14:00 ... hey, foo, it's username. nice to see you at (14:00:00)! EOF FILES
$HOME/.wuzzah the default file containing the list of users to watch BUGS
don't know of any, but reports (and patches too) are always welcome. feel free to send them to the author. AUTHOR
sean finney <seanius@seanius.net> sean finney Sun Nov 17 02:41:45 EST 2002 wuzzah(1)
All times are GMT -4. The time now is 02:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy