Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0006203opensim[REGION] OpenSim Corepublic2012-08-14 14:582019-02-25 07:44
ReporterSignpostMarv 
Assigned Totampa 
PrioritylowSeverityminorReproducibilityalways
StatusresolvedResolutionno change required 
PlatformOSOS Version
Product Versionmaster (dev code) 
Target VersionFixed in Version 
Summary0006203: opensim create region command provides default values it should know to be invalid
Descriptionthe `create region` command provides two defaults that it should immediately know are invalid- the region coordinates and the port number.

Preferably, OpenSim when in standalone mode should:

a) not suggest region coordinates for a space already occupied by a running region.
b) not suggest port numbers already used by the opensim process.

Optionally:
1) not suggest region coordinates for a space already occupied by a region when in grid/robust mode
2) not suggest port numbers already used by other applications
Steps To Reproduce1) Launch standalone
2) create a region, accepting all defaults (unique names may or may not be an issue)
3) repeat step 2
Tagsgo here
Git Revision or version number4bbdcfb5ee81f459df9ff9a2ac477f6419cfc279
Run Mode Standalone (Multiple Regions) , Grid (Multiple Regions per Sim)
Physics EngineBasicPhysics
EnvironmentMono / Linux32, Mono / Linux64, Mono / Windows, Mono / OSX, .NET / Windows32, .NET / Windows64
Mono VersionNone
Viewer
Attached Files

- Relationships

-  Notes
(0034851)
tampa (reporter)
2019-02-25 07:44

Granted the registration failure is not very graceful in handling duplicate coordinate registration it nonetheless provides the needed info on how to resolve the conflict.

As for in-use ports, this would require deep network scanning on NAT and quite a lot of work to make OS independent. It is frankly down to the administrator to properly handle their network and handle the port allocations properly.

Resolving because this level of idiot-proofing goes a bit beyond the scope of the project as of now.

- Issue History
Date Modified Username Field Change
2012-08-18 04:32 DMX04 New Issue
2012-08-18 04:32 DMX04 Issue generated from: 0006159
2012-08-18 04:37 DMX04 Tag Attached: go here
2019-02-25 07:44 tampa Note Added: 0034851
2019-02-25 07:44 tampa Status new => resolved
2019-02-25 07:44 tampa Resolution open => no change required
2019-02-25 07:44 tampa Assigned To => tampa


Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker