On 13-Feb-98 Bodo Bauer wrote:

...

The only thing I haven't added yet is a way to kick this script after an automatic redial.

My multidialer won't continue until connected. Put your script sequentially after the call to my script and it will continue if connected (actually if connected or timed out. You can check the return code) By the responses, it sounds like this won't be necessary, anyways! I may stick a call to lynx to dump my usage time page to a file (or mail to me, even better) each time mail is fetched.

You can also use 'diald', which works perfect for me. (In fact, our office has been connectet to the internet via a diald controlled PPP link. But since last week we have our T1 up and running and no dialing is needed any more...:)

I had diald up and functional, but I don't want the port to be that sensitive. Sometimes ping (or something else) would get zombied somehow and constantly be bringing up the connection. I only have 10 hours on the account per month, so I didn't want it to dial without supervision! I put this script in my crontab and it fetches my mail while I sleep! I had to hack a whole lot more to get this to happen in OS/2, and not at all in Whine 95. --- Jonathan Markevich Tax reform means "Don't tax you, don't tax me, tax that fellow behind the tree." -- Russell Long -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e