Linux 2.0.33 libc5.
diald 0.16 + patch 0.16.5
dialmon 0.6
I start diald and dialmon separately (don't use dialmon to trigger
diald);
% ps ax|grep dial
22692 ? S 0:02 diald
23295 ? S 0:00 dialnsl
23296 ? S 0:01 /usr/sbin/dialmon -b50000
When I start dialmon all is ok, the log says:
===========
Jan 8 07:22:21 i3 diald[253]: FIFO: full monitor connection to
monitor /tmp/diald.info requested
Jan 8 07:22:21 i3 dialmon[266]: connection from pc45
Jan 8 07:22:24 i3 dialmon[266]: connection from pc11
Jan 8 07:22:25 i3 dialmon[266]: connection from pc15
....................
=
Then , randomly, there are problems with diald writing to the
/tmp/diald.info pipe or dialmon reading from it.
===========
...
Jan 8 14:31:43 i3 diald[22692]: Writing error on pipe
/tmp/diald.info: Try again.
Jan 8 14:32:14 i3 last message repeated 620 times
Jan 8 14:33:15 i3 last message repeated 3889 times
Jan 8 14:34:16 i3 last message repeated 3264 times
Jan 8 14:34:49 i3 last message repeated 825 times
When this happens the win95 clients can't see the real situation of
the link with the dialmon client, because it doesn't receive status
messages from the Linux server for a while.
I can't reproduce the error at my will, it happens every now and then.
Be it diald or dialmon fault, are there any solutions?
Thanks.
--
Giulio
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
