On Tue, 16 Mar 1999, Mike Jagdis wrote:
> On Sun, 14 Mar 1999, Ed Doolittle wrote:
>> Hmm, doesn't diald check to see that the PID actually corresponds to a
>> running process?
> No. Diald writes the pid to a file if asked but it doesn't use
> it for locking itself out.
diald is sometimes started manually, though. Some kind of
locking might be a nice feature to prevent multiple dds from
starting with the same conf file. As it stands, if someone
forgets to change the pidfile, it just gets overwritten, in
which case changes in run level may result in a second default
dd trying to start.
>> 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?)
> No. I flatly refuse to fix broken distributions by kludging
> the code around. I expect people getting paid to do some commercial
> quality scripting to GET IT RIGHT!!!
I hear you ... I must admit it wasn't one of my better ideas.
:-)
> I *may* put my own start up and connect scripts in the next
> diald release - but I'm not sure the commercial sector deserve
> free hand outs to fix their own stupidity :-).
Some of us still build our own "distributions", so good startup
scripts are nice to have.
Ed
--
Ed Doolittle <mailto:[EMAIL PROTECTED]>
"Everything we do, we do for a reason." -- Peter O'Chiese
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
