• doors & disconnected users

    From Chris Trainor@DIGDIST/LINGNET to All on Wed Aug 1 12:55:38 2012
    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.

    Thanks,
    --Chris

    ------------------------------------------
    | Chris Trainor - FleetHQ BBS
    | telnet://bbs.fleethq.org
    | http://www.facebook.com/FleetHQ
    | +1-401-949-0465 (V.34/HST/CrankyAtTimes) ------------------------------------------

    ---
    ■ Synchronet ■ FleetHQ BBS - Greenville, RI
  • From echicken@DIGDIST/LINGNET to Chris Trainor on Wed Aug 1 15:11:41 2012
    Re: doors & disconnected users
    By: Chris Trainor to All on Wed Aug 01 2012 12:55:38

    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.

    echicken
    electronic chicken bbs - bbs.electronicchicken.com - 416-273-7230

    ---
    ■ Synchronet ■ electronic chicken bbs - bbs.electronicchicken.com
  • From Chris Trainor@DIGDIST/LINGNET to echicken on Wed Aug 1 15:58:54 2012
    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.


    thanks,

    --Chris

    ------------------------------------------
    | Chris Trainor - FleetHQ BBS
    | telnet://bbs.fleethq.org
    | http://www.facebook.com/FleetHQ
    | +1-401-949-0465 (V.34/HST/CrankyAtTimes) ------------------------------------------

    ---
    ■ Synchronet ■ FleetHQ BBS - Greenville, RI
  • From Digital Man@DIGDIST/LINGNET to Chris Trainor on Wed Aug 1 16:50:51 2012
    Re: doors & disconnected users
    By: Chris Trainor to All on Wed Aug 01 2012 12:55 pm

    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.

    Are you sure that "oonode.dat" is a "lockout file"? That doesn't sound like a 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').

    digital man

    Synchronet "Real Fact" #72:
    SyncTERM (created by Deuce) contains portions of Synchronet and SEXYZ code. Norco, CA WX: 82.6°F, 41.0% humidity, 11 mph WNW wind, 0.00 inches rain/24hrs

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From Digital Man@DIGDIST/LINGNET to Chris Trainor on Wed Aug 1 16:52:36 2012
    Re: doors & disconnected users
    By: Chris Trainor to echicken on Wed Aug 01 2012 03:58 pm

    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.

    If the door is configure as non-native, then the clean-up command-line will be executed as a non-native (i.e. 16-bit DOS) program as well.

    digital man

    Synchronet "Real Fact" #24:
    The Digital Dynamics company ceased day-to-day opperations in late 1995.
    Norco, CA WX: 82.6°F, 41.0% humidity, 11 mph WNW wind, 0.00 inches rain/24hrs

    ---
    ■ Synchronet ■ Vertrauen ■ Home of Synchronet ■ telnet://vert.synchro.net
  • From Chris Trainor@DIGDIST/LINGNET to Digital Man on Thu Aug 2 18:50:27 2012
    Re: doors & disconnected users
    By: Digital Man to Chris Trainor on Wed Aug 01 2012 16:50:51

    Are you sure that "oonode.dat" is a "lockout file"? That doesn't sound like likeout file name to me, but who knows?

    Yeah, the file just contains text that says someone is on. It's deleted
    by the game when you gracefully exit.


    Setting the door to single-user/player in SCFG will automatically prevent multiple users from running the door simultaneously (i.e. not 'dangerous').

    Ok cool, i'll just do that and get rid of trying to have the game
    enforce it as well.

    Thanks,
    --Chris

    ------------------------------------------
    | Chris Trainor - FleetHQ BBS
    | telnet://bbs.fleethq.org
    | http://www.facebook.com/FleetHQ
    | +1-401-949-0465 (V.34/HST/CrankyAtTimes) ------------------------------------------

    ---
    ■ Synchronet ■ FleetHQ BBS - Greenville, RI