> I ran the ps aux command when it had booted and had not totaly started.
It looks like diald is running after all. It may not be
configured correctly, but it certainly is running (otherwise it wouldn't
show up when you run ps).
> I ran the ps aux command after killing the above process and then
> starting diald from the command prompt. Here is the output then:
The difference in output is cause by the fact that you start it at
a different time, after other processes have launched, etc. Type "man ps"
for details on what the columns mean.
> the process appears to be working but if I go to the X display and run dctrl
> it does not respond.
Perhaps there is a problem with dctrl, or the permissions of the
FIFO pipe...? Did the diald FAQ have anything to say about this?
> After killing the process and restarting it from the command line
> dctrl responds normally. I tried to set UID to root to see what if
> any difference this would have. No difference.
Don't know what to say. My intuition says it may have something
to do with the environment diald is starting up in within your boot
scripts, or else a problem with a FIFO. Who is the diald maintainer? Can
he offer any other advice?
--Derek
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
