I'm assuming that closing the terminal would cause the same reaction user hanging-up - if not, then maybe it's just a local login issue.
No, its not and this is exactly why its happening.
When you force a terminal to close, it doesn't tell the applications running within it to shutdown. You are essentially forcefully killing Mystic when you do that.
I can trap whenever you click "X" to shutdown a terminal in Linux.
cases, 3/4ths of the time I get ghosted & I end up emailing Zero Reader requesting to have him kill the session for me. <- that's the bigger
deal.
I can trap whenever you click "X" to shutdown a terminal in Linux.
I appreciate it, and that will be useful. But I was trying to expose a similar "ghosting" issue that I've been experiencing with Alcoholiday. I
reach the inactivity timeout that the BBS has set. I assume that will be the deciding factor of whether or not you are actually connected. Now if you're in a door that might not happen.
How long do you stay ghosted? What OS is Alcoholiday?
eventually released. I'm just curious if you are giving Mystic time to reach the inactivity timeout that the BBS has set. I assume that will be
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 98 |
Nodes: | 16 (1 / 15) |
Uptime: | 08:45:30 |
Calls: | 3,541 |
Calls today: | 2 |
Files: | 8,461 |
Messages: | 337,685 |