Bernd wrote:
On Saturday, 20 September, 2003 16:35, Carlos E. R. wrote:
The 03.09.19 at 10:46, Bernd wrote:
In these previous logs I've saved over the last month+, I find more random drop times, yet half still apply to the "top of the hour". Except for the fact that I can't stay connected longer than 59.4 min, overall, it still seems random.
You could try to automate getting all connect, disconnect and on time, and graph frequencies - I'd use OO for that. If there is a certain rough similarity in times, that's something you can show your provider.
Unfortunately, it's not my ISP. I got another ISP to give me a test account for the day. I got a (SIGHUP) to pppd after 58.1 minutes. Soooo... It's on my side, or it's the modem itself.
I have been busy elsewhere (building a computer for a friend of mine) and haven't been reading the thread and if you have already done what I suggested some time ago then you can send me an abusive e-mail :-). You said above "or it's the modem itself." One of the things I suggested was for you to get hold of another modem and see if you still come up with the same problems. I think in an earlier message you said that you would try and (?)borrow another modem for this purpose but I don't know if you did. The other thing, what exactly is the initialising string(s) that you send to the modem in SuSE?
If I could only track the source of the (SIGHUP)!!!
Any of the ideas I told you were any good? strace, ltrace and such?
I did try strace. I got 548 lines of output in 30 seconds of tracing, and then it exited.
Perhaps you could post a new question on how to trace signals, maybe some one knows and notices the question. Or post it on some technical/programming list -- I think there is one on SuSE. not sure -- and if you get to know that, tell me, I'm interested :-)
I'll give this a go.
Thanks for everything!!!
Bernd
Cheers. -- Hire teenagers while they still know everything.