SphereServer BugTracker - SphereServer
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001786SphereServernew feature requestpublic28-07-10 06:0219-08-10 05:12
Reporterumuri 
Assigned ToShiryuX 
PrioritynormalSeverityminorReproducibilityN/A
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version0.56c Nightly 
Target VersionFixed in Version0.56c Nightly 
Nightly VersionNot Available
Experimental FlagsNone
Option FlagsNone
Internal Build Number
Summary0001786: Prevent Telnet from resync pausing.
DescriptionDue to resolution of issue 0001785 as intended and deprecated functionality, can the option to initiate a resync pause(via r, not resync) be completely disallowed from remote connections?

It seems rather unwise to leave a "feature" that can entirely hang a shard if activated until someone with physical server access is present especially as this .
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
related to 0001785closed  Telnet thread stopped during resync, cannot resume 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
28-07-10 06:02umuriNew Issue
28-07-10 06:02umuriNightly Version => Not Available
28-07-10 06:02umuriExperimental Flags => None
28-07-10 06:02umuriOption Flags => None
18-08-10 22:08ShiryuXRelationship addedrelated to 0001785
19-08-10 05:12ShiryuXStatusnew => resolved
19-08-10 05:12ShiryuXResolutionopen => fixed
19-08-10 05:12ShiryuXAssigned To => ShiryuX
19-08-10 05:12ShiryuXNote Added: 0000573

Notes
(0000573)
ShiryuX   
19-08-10 05:12   
Seems logical, the server won't listen to any client in a resync pause, so a client should not be able to start something he can't finish. Of course, is also logical to use resync instead, but a safety check won't hurt anyone :P


- Modified 0001786: Disabled 'r' console command to be used by remote telnet, use 'resync' instead.
  Any other way to access the console (physical or remote desktop) can still use it.