#Time OUT!
11 messages in this thread
Here is an idea! I would feel alot safer if after a certain time passes and
nothing comes to the screen, that the program logs itself off. Even if that
means doing a old fashioned +++ thingie. I have had this happen, line noise,
or me giving a Signame that does not exist. What happens, Whap just hangs
around after getting an error. If I was away (or asleep) CI$ is would be makin
the big bucks!
Is this a possibility?
-mark= Amiga – The Right Choice.
Mark,
I have that same feeling… I can just see the $$$'s rolling by as Whap! gets
stuck by a CIS error or glitch somewhere. Nothing against Whap! mind you – I
think it's a GREAT program, and very much needed, but it does scare me a little
to hit the go button and then hit the sack hoping all goes well.
Allen
That bothers me too. I wonder if Jim can comfort us any? 🙂
Well Henry, I dunno. I just downloaded your message (among the rest) while
doing some kitchen work (downstairs) and everything worked fine
unattended….this time anyway. I wonder if there is anything kind of timer in
Whap! so that…say a five minute period of no action would cause Whap! to log
off.
Allen
I'm not sure, but I believe Whap! does do that, eventually. If it attempts a
GO FORUM and doesn't get a response in two minutes, for example, it attempts to
go to the next forum in the list.
Even if Whap! doesn't, though, CIS does. The idle time period varies depending
on where you are; in CO (where you might be "listening" only in a formal
conference) for example, the timeout period is one hour. In other places it's
10 to 15 minutes. I'm not sure if this is universally implemented, but I've
never gotten permanently stuck.
Rick
Rick,
What happens then? Does CIS log you off, send a 'how come you ain't doin
nuthin' message, or what?
Thanks,
Allen
In the case of CO (which burned me a few times before I found out you have to
occasionally issue a /UST CO or something to let you know it's alive), it posts
a brief "logged off due to inactivity" message (I forget the exact wording),
and logs you off, yes. As for the other locations, can't say as I recall, as
it doesn't catch me very often.
Rick
Rick,
That's why I was wondering as I've haven't (fortunately) experienced it
myself either.
Thanks,
Allen
While attempting to "get messages" from all my forums this afternoon,
WHAP hung because AMIGAARTS was "unavailable". I was fixing lunch while my AMI
was working and I know that it was still setting idle after about 20 minutes.
This might be an unusual occurance but I thought I'd mention it.
Bill Rogers — Canton Ohio
I don't know how Whap! works that out. I hit AmigaArts during the same
"maintenance" period. After 2 minutes, Whap! issued the next command in my
string, which was GO AMIGATECH. It never seemed to go anywhere beyond that
point. I would have thought that it would have issued the NEXT command after
another two minutes, and so on. Guess I'll have to defer to Jim on this
subject, as I'm only a Whap! user like you.
Rick
Sure .. how about two new fields in the setup menu:
1. Inactivity Timeout (in minutes)
2. Disconnect string (varies from modem to modem)
-Paul