#/etc/init.d/inetsvc stop
#/etc/init.d/inetsvc start
or
#pkill -HUP xinetd
Which works if youve substituted xinetd for the stock inetd in your
Sun-supplied init.d scripts...
>or
>
>#pkill -HUP xinetd
which works if youre running a version of xinetd that reconfigures itself
based on the HUP signal. older versions (which you shouldnt be running
due to various security issues) of xinetd caught SIGUSR1 or SIGUSR2 as
their reconfiguration signal.
-tom
--
"You can only be -so- accurate with a claw-hammer." --me
is the following correct ?
KILL -USR1 xinetd
kill -USR2 xinetd
and what's the difference between pkill and kill?
> if I want to send SIGUSR1 or SIGUSR2 signal
>
> is the following correct ?
> KILL -USR1 xinetd
No, "kill" should be in lower case.
> kill -USR2 xinetd
No, "kill" requires a PID (so "kill -USR1 12345" would work, "kill -USR1
foo" wouldn't.)
>
> and what's the difference between pkill and kill?
kill, as I mentioned, requires a PID (or a list of PIDs). So
traditionally you'd do something like
ps -ef|grep xinetd
then make a note of the PID (remembering to ignore the PID of the grep
command that you'll almost certainly see), then kill -WHATEVER that_PID
pkill, delivered with Solaris 7 and later, effectively stops you needing
to grep for the PID - you simply say
pkill -USR1 xinetd
to send a SIGUSR1 to all processes whose name contains "xinetd".
It's more convenient than kill because you don't get extraneous things
like the PID of the grep command. You can also add command line options
to match patterns, to limit the search to processes run by a certain
user, and so on.
The manual page for pkill and pgrep (which is similar but just displays
the PIDs rather than sending signals to them) will tell you more.
--
Tony Walton
The truth is out there. The lies are inside your head.