[not a guru - just a user - I could be completely wrong here]
> Hmm, doesn't diald check to see that the PID actually corresponds to a
> running process?
No because it normally doesn't create one. That's usually done by the init
script.
> I have three suggestions of ways to avoid that scenario (maybe these
> already hold, I haven't checked):
>
> 1) Diald should check that the diald PID in the pidfile actually
> corresponds to a running *diald* process
OK write detection into the init script. :) But note that it happens before
diald is ever started.
> 2) If the process is a diald process, make sure it isn't
> itself (otherwise just touch the pidfile and leave it alone)
diald is not running yet, it doesn't have a pid number to compare against.
> 3) Diald should switch pids after a certain amount of time to
> get a random
> higher pid number which would be less likely to interfere
> with the boot
> process. (Is it possible for a process to change pids
> without forking?)
It didn't create the pid so why should it keep making new ones? I don't
want to think of the headaches of doing this on a running connection
session.
Note: diald itself seems to ignore pid files altogether. (I've had lots of
concurrent diald sessions.) This is a initialization script issue.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
