Date: Sat, 21 Jan 2012 15:19:10 +0200 From: =?windows-1251?B?yu7t/Oru4iDF4uPl7ejp?= <kes-kes@yandex.ru> To: Frank Shute <frank@shute.org.uk> Cc: freebsd-questions@freebsd.org Subject: Re[2]: problem to kill -KILL process Message-ID: <909294609.20120121151910@yandex.ru> In-Reply-To: <20120121092459.GB8988@orange.esperance-linux.co.uk> References: <1712857962.20120120232421@yandex.ru> <20120121092459.GB8988@orange.esperance-linux.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Здравствуйте, Frank.
Вы писали 21 января 2012 г., 11:24:59:
FS> On Fri, Jan 20, 2012 at 11:24:21PM +0200, ??????? ??????? wrote:
>>
>> Hi
>>
>> # ps ax|grep rad
>> 45471 ?? T<Ls 263:35.44 /usr/local/sbin/radiusd
>> 26473 1 S+ 0:00.00 grep rad
>> flux# date
>> Fri Jan 20 23:20:28 UTC 2012
>> flux# kill -KILL 45471
>> flux# date
>> Fri Jan 20 23:20:41 UTC 2012
>> flux# kill -KILL 45471
>> flux# date
>> Fri Jan 20 23:20:54 UTC 2012
>> flux# kill -KILL 45471
>>
>>
>> top
>> 9 root 16 - 0K 8K syncer 2 7:12 0.00% syncer
>> 45471 freeradius 20 -20 311M 283M STOP 0 3:38 0.00% {radiusd}
>> 49114 root 21 0 10460K 4240K select 0 2:43 0.00% zebra
>>
>> How to kill process without reboot?
>>
FS> Doesn't radius have a script in /usr/local/etc/rc.d?
FS> If so use that to stop it rather than KILLing it. E.g:
FS> # /usr/local/etc/rc.d/radiusd stop
despite on it uses standart rc.subr, which says:
# stop if ${pidfile}
# rc_pid=$(check_pidfile $pidfile $command)
# else
# rc_pid=$(check_process $command)
# kill $sig_stop $rc_pid
# wait_for_pids $rc_pid
# ($sig_stop defaults to TERM.)
in other words: kill -TERM 45471 in my case
FS> or something like that.
man kill
......
Some of the more commonly used signals:
......
9 KILL (non-catchable, non-ignorable kill)
Standart tool do not do its job. It can not stop/kill processes.
--
С уважением,
Коньков mailto:kes-kes@yandex.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?909294609.20120121151910>