On Sat, Jun 11, 2005 at 08:56:06PM +0100, Jonathan Buzzard wrote:
>
> [EMAIL PROTECTED] said:
> > The problem is that the KILL(2) call is used to check to see if a process
> > exists at the specified PID. The default action for SIGUSR1 is to kill the
> > targeted process. Thus the original process
[EMAIL PROTECTED] said:
> The problem is that the KILL(2) call is used to check to see if a process
> exists at the specified PID. The default action for SIGUSR1 is to kill the
> targeted process. Thus the original process dies, and the new process exits.
>
> The propper thing to do is to use kill
I think you may have misunderstood this bug report.
As I understand it the code is intended to check for a lock. If the lock is
there and the old pid still exists the new process should die. Otherwise
remove the old lock and continue.
The problem is that the KILL(2) call is used to check to s
[EMAIL PROTECTED] said:
> It is obvious that the way the program is behaving the bug report is they it
> is programmed to behave. I would like to know if there is a better way to
> handle this.
It is a bogus bug report, and probably stems from a lack of understanding
of exactly what hotkey does
Bug #153070 [0] was reported a few years ago. I am now the maintainer
of toshutils and am trying to resolve this bug. I can reproduce it
very easily. Thing is I am not sure if this is really a bug or if it is
the correct behavior. Essentially, if the pid file already exists in
/var/tmp and
5 matches
Mail list logo
