Tim,
Thanks for the feedback. I have managed to get diald to start using some earlier
replies. However, your comments raise some good points:
>
>Just to make sure -- you printed out messages to show that it was not
>returning? If so, did you make sure you flushed the output? I know
>it's kind of silly, but I make that mistake all the time.
>
I was using the function in pppd which writes to the log file - I hope it flushes the
output.
>
>Have you got this working with pppd sans diald? Is there any process
>which could be holding onto /dev/ttyS0?
pppd always worked properly when started manually, it was just when diald was used
that I had problems. It is possible, I guess, that something could be holding
/dev/ttyS0 but I can't think of anything.
>This seems very strange to me. I find it doubtful that the bug is
>in pppd, but from what you're saying it sounds like pppd is getting
>the right information and dying. I'm not sure, however, why open()
>is hanging like that.
>
John Adams' suggested change to pppd to get round the file open problem works.
However, since the problem only shows up when diald is used with pppd there seems to
be some strange interaction between the two programs that causes the problem.
Iain
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
