SphereServer BugTracker - SphereServer
View Issue Details
0001785SphereServerexecutable - genericpublic26-07-10 11:3727-07-10 17:23
umuri 
 
normalmajoralways
closedno change required 
0.56c Nightly 
 
Not Available
New_Triggers, UseNetworkMulti
FileCommands, Buffs
0001785: Telnet thread stopped during resync, cannot resume
When you resync via the telnet console, the telnet console can no longer send the second R command to wakeup from resync, using latest nightly build.

Tried all combination of network and telnet related ini settings, including ones only vaguely related, log, filter, async, and all EF flags.
 
Could not find a workable combination that allows proper resyncs via telnet.
No tags attached.
related to 0001786resolved ShiryuX Prevent Telnet from resync pausing. 
Issue History
26-07-10 11:37umuriNew Issue
26-07-10 11:37umuriNightly Version => Not Available
26-07-10 11:37umuriExperimental Flags => New_Triggers, UseNetworkMulti
26-07-10 11:37umuriOption Flags => FileCommands, Buffs
26-07-10 22:45umuriNote Added: 0000527
26-07-10 23:33umuriNote Added: 0000528
27-07-10 17:23MrSugarCubeStatusnew => closed
27-07-10 17:23MrSugarCubeNote Added: 0000529
27-07-10 17:23MrSugarCubeResolutionopen => no change required
18-08-10 22:08ShiryuXRelationship addedrelated to 0001786

Notes
(0000527)
umuri   
26-07-10 22:45   
Umm, quick note.

This only affects the resync pause done with R, not the resync command. (Stupid me never knew a resync command was added, (51a veteran))
(0000528)
umuri   
26-07-10 23:33   
Found a workaround for the issue, so i guess it can be downgraded from major to minor, since resync does technically still work.

turn on telnet packet filter in options and add:
PACKET114=f_telnet_resync_block

and

[function f_telnet_resync_block]
//Packet 114
if ( <local.0> == 072 ) && ( <local.num> == 03 )
    serv.log Resync blocked to prevent telnet from hanging the server!
    return 1
endif

Blocks R to start the resync pause, but allows resync to do the full cycle.
(0000529)
MrSugarCube   
27-07-10 17:23   
There isn't really anything wrong going on here. Sphere won't process any client data received during a resync pause, so if you're going to resync from a client then (as you've already found out) you should be using the 'resync' command.