"Robert C. Paulsen, Jr." wrote:
>
> "Ed G." wrote:
> >
> > > But the current problem is this: It runs fine for a few days (3-5) then
> > > all of a sudden quits working. When I say "quits working" I mean one time
> > > I send out some packets it will bring up the link to my ISP then all of
> > > a sudden the next time it won't. it continues to "not work" until I kill
> > > diald and restart it, after which it is fine again for a few more days.
> >
> > Yes, I have noticed the same behavior on my LRP setup and found
> > it infuriating: it makes diald worse than useless, IMO.
> >
> > Frankly, I wonder if the problem doesn't have something to do with
> > the 2.0.36 kernel. Does your RH 5.2 use 2.0.36 perhaps?
> >
>
> I had a similar problem with the older diald (0.16) when I upgraded
> from a 2.0.x kernel to a 2.2.x kernel. When I upgraded to the latest
> diald (0.99.1) all worked fine.
>
> I suspect that the only working combinations are:
>
> kernel diald
> 2.0.x 0.16
> 2.2.x 0.99.x
>
> While I had a mis-matched configuration, I "solved" the problem with
> the following crontab script that ran every 15 minutes:
[...]
This wouldn't work for me: diald is still present in the process list.
diald (or the kernel) just stops.
S.
--
If at first you don't succeed, skydiving isn't for you
Simon Burley, Double Negative Ltd, London.
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
