On Fri, Dec 16, 2005 at 10:52:25AM +0300, roma.a.g wrote:
> Is there anyone who can explain me, why when i say 'kill -HUP id', and its
> failed to restart, kill say nothing?
That's because all kill is responsible for is sending the signal;
see kill(2).
As to whether or not the process in questio
In the last episode (Dec 16), Roman Gorohov. said:
> Oliver Fromme wrote:
>
> > roma.a.g <[EMAIL PROTECTED]> wrote:
> >> Is there anyone who can explain me, why when i say 'kill -HUP id',
> >> and its failed to restart, kill say nothing?
>
> > There is no way for the kill command
Roman Gorohov. <[EMAIL PROTECTED]> wrote:
> Thanks for your reply. My question was about standard bsd daemons, not
> about some apps with unpredictable behaviour.
But the kill command doesn't know what kind of daemon it
is sending a signal to. It just sends a signal to a PID.
That PID could bel
Oliver Fromme <[EMAIL PROTECTED]> wrote:
> roma.a.g <[EMAIL PROTECTED]> wrote:
> > Is there anyone who can explain me, why when i say 'kill -HUP id',
> > and its failed to restart, kill say nothing?
>
> Because the kill command has no way to know about it.
>
> The kill command only instruc
roma.a.g <[EMAIL PROTECTED]> wrote:
> Is there anyone who can explain me, why when i say 'kill -HUP id',
> and its failed to restart, kill say nothing?
Because the kill command has no way to know about it.
The kill command only instructs the kernel to deliver
a signal to a process (or to a proc
> Is there anyone who can explain me, why when i say 'kill -HUP >
> id', and its failed to restart, kill say nothing?
> It is such an easy to implement...
Your application could be choosing to ignore SIGHUP
(restarting on SIGHUP is a convention, not a OS defined
requirement)?
--
FreeBSD Volunteer
6 matches
Mail list logo
