10-25-2012
Thanks for your example :-)
There is still a problem, because I can't call "kill" on a remote machine. Hence, I can only call a remote script that sends the signal to the remote process. Is It better to call the process by name or by process ID? Will the process ID be constant after reboot?
6 More Discussions You Might Find Interesting
1. Programming
I was hoping someone could assist me on a text-based instant messaging client(using UDP) I am working on. I have the network communication basics already in place but, specifically, needed some further help on the "messaging other users" and "getting a user list" functions. The server code that... (0 Replies)
Discussion started by: AusTex
0 Replies
2. IP Networking
this id the message i get with a suggestions to check those files:
/etc/src.sh
/etc/hosts
/usr/adm/inetd.sec
i have little knowledge of hoe to edit those files/
i went to the etc library and didn't found src.sh file.
what should i do?
also didn't find the inetd.sec file
In the host... (3 Replies)
Discussion started by: amirp
3 Replies
3. UNIX and Linux Applications
hi guyz i work as a system administrator for some organization(am a newbie). one of the solaris machines is loaded with the messenger server...all configured by a former administrator. my task was to create user accounts for the mail and calendar services and as i checked its not working .....i... (0 Replies)
Discussion started by: henokia4j
0 Replies
4. Programming
hi
I am using posix functions such as mq_open, mq_close and including the mqueue.h. but its giving a linking error,"undefined reference to mq_open and mq_close".
it it that we have to link some library or so while compiling... plzzz help
Thanxs
Mohit (0 Replies)
Discussion started by: mohit3884
0 Replies
5. UNIX for Advanced & Expert Users
Hello All,
I am getting " The DT messaging system could not be started" message when wants to login as root on a box running on tru64 5.1A.
/etc/hosts is ok.
when i see in .dt/errorlog it shows message server could not be started.
Thanks for help.
Awadhesh (2 Replies)
Discussion started by: Awadhesh
2 Replies
6. Shell Programming and Scripting
Good Morning,
Users can no longer log into SunBlade 2500 Solaris 9 system (though root still can). Here's what I'm getting and what I've done. I'm most suspicious of the full drive since that pops up twice and I did see one looks full. What's a good way to reduce what's on it?- or.. what else... (2 Replies)
Discussion started by: Stellaman1977
2 Replies
killall(1M) killall(1M)
NAME
killall - kill all active processes
SYNOPSIS
[signal]
DESCRIPTION
is a procedure used by to kill all active processes not directly related to the shutdown procedure.
is chiefly used to terminate all processes with open files so that the mounted file systems are no longer busy and can be unmounted. sends
the specified signal to all user processes in the system, with the following exceptions:
the process;
all processes (including background processes) associated with the terminal from which was invoked;
any process, if owned by
any process, if owned by
any process;
any process;
any process.
obtains its process information from and therefore may not be able to perfectly identify which processes to signal (see ps(1)).
If no signal is specified, a default of (kill) is used.
is invoked automatically by The use of is recommended over using by itself (see shutdown(1M)).
FILES
SEE ALSO
fuser(1M), kill(1), ps(1), shutdown(1M), signal(5).
STANDARDS CONFORMANCE
killall(1M)