| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 42 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 35:14:24 |
| Calls: | 235 |
| Files: | 846 |
| Messages: | 124,255 |
quick question. What's a good way to handle (on Synchronet) users that disconnect while in a door? I've run into an issue where in Operation Overkill, if a user drops out whle playing the oonode.dat file doesn't
get cleaned up. That file being there will prevent other users from logging in. Any ideas how to clean that up if someone just drops
carrier? (well, closes their synchterm window).
Have you tried using the "Clean-up Command Line" option in SCFG for that external? You should be able to run a batch script or a specific command to remove that file. IIRC, this will run whether the door exits gracefully or not.
Hi all,
quick question. What's a good way to handle (on Synchronet) users that disconnect while in a door? I've run into an issue where in Operation Overkill, if a user drops out whle playing the oonode.dat file doesn't
get cleaned up. That file being there will prevent other users from
logging in. Any ideas how to clean that up if someone just drops
carrier? (well, closes their synchterm window).
One idea I had was to set it in Overkill that it's single node, then
flag it as non-multiplayer in synchronet. That I think would prevent overkill from even creating the lockout file. But, that could be 'dangerous' to the game if by some chance 2 users managed to login at
the same time.
Re: doors & disconnected users
By: echicken to Chris Trainor on Wed Aug 01 2012 15:11:41
Have you tried using the "Clean-up Command Line" option in SCFG for that external? You should be able to run a batch script or a specific
command to remove that file. IIRC, this will run whether the door exits gracefully or not.
OK cool. I thought of that actually but wasn't sure if it was called on disconnect, or how the command line was handled. So if the door is a dos app, this can just be another batch file in the same location as the
door that I call? Easier would be if I just put in the del
d:\filename.ext command or a native rm /path/doors/game/filename.ext.
Are you sure that "oonode.dat" is a "lockout file"? That doesn't sound like likeout file name to me, but who knows?
Setting the door to single-user/player in SCFG will automatically prevent multiple users from running the door simultaneously (i.e. not 'dangerous').