Derek,
I looked at the faq and it talked about the fifo having to be able to be ran
from the user starting diald. I put a set of commands in rc.local to rm -f the
fifo and then start diald. No difference. I set UID to root with no change in
behavior. If I start 2 occurances from the rc.local, 9 out of ten times one of
them will work OK. But sometimes they both try to work and compete with each
other for the modem, then neither work correctly. Running out of ideas. Don't
know what else to try. Starting Diald from a shell in the background with sleep
commands didn't seem to have any effect. Need a reliable way to do this as I am
not the one always starting the machine, and no one else has the knowledge to let
have the root password at work and my wife doesn't want to learn unix so that she
can get on the internet at home when I am not there.
Any suggestions would be greatly appreciated.
Thanks
Vic Lepouce
Derek Simkowiak wrote:
> > 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]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
