| Commit message (Collapse) | Author | Files | Lines |
|---|
|
* This patch aims to introduce look at direction persistence between logins. It won't be active until the second part of the patch is committed in about two weeks time. At
this point, region servers that haven't upgraded past this revision may run into problems
* This checkin upgrades the user database. As always, we recommend you have backups in case something goes wrong.
* Many thanks to tyre for this patch.
|
|
|
|
same as the original login region
|
|
* This may possibly (est. 20% change) help the situation that we see on OSGrid meetings when a region stops accepting logins, which appears to be because it never receives the expect_user request
|
|
* Now it should properly inform the user and stop a login if a region server could not be contacted in order to expect a user (the last commit didn't actually quite work correctly)
|
|
emergency region login code is a cut and paste job of the preceding normal region login code
* also, properly tell the user if no region can be contacted, rather than letting the login proceed only to fail later when authentication fails on the region side
* copying and pasting code... it makes me cry inside... so sad...
|
|
selected region fails, rather than swallowing it
|
|
process easier
* documentation
|
|
Thank you, Xugu Madison and ChrisDown, for a patch that
fixes linux filename extensions from .Xml back to .xml
|
|
* This is a HUGE OMG update and will definitely have unknown side effects.. so this is really only for the strong hearted at this point. Regular people should let the dust settle.
* This has been tested to work with most basic functions. However.. make sure you back up 'everything' before using this. It's that big!
* Essentially we're back at square 1 in the testing phase.. so lets identify things that broke.
|
|
The attached patch (against r6075) fixes it for grid-mode. If the
home-region isn't available, the stored regionHandle will be used
to compute the region-coordinates of the home. This will be wrong
if the home-region has moved, of course, but without the region
being online we can't request the RegionInfo of it for finding out.
Doing that (before the patch) and accessing the (null) RegionInfo
led to a NullReferenceException, which prevented logging in to the
last location.
|
|
* I can't see why the last compile failed - hoping it's some kind of glitch
|
|
|
|
|
|
to make it easier to work with.
|
|
|
|
than displays information directly
|
|
currently on Forge in a nice, friendly modular format.
* There are a lot of changes and this is quite experimental. It's off by default, but you can turn it on by examining the bottom of the opensim.ini.example for the proper OpenSim.ini settings. Remember, you still need an agent domain..
* Furthermore, it isn't quite right when it comes to teleporting to remote regions (place_avatar)
|
|
The attached patch fixes that your home-location icon is
displayed on the region you logged in, not on your home-region.
|
|
|
|
Common.Communications for now (since this was the only class in that project)
|
|
|
|
|
|
This will have no effect unless both the UGAI and the region are
this revision or later
|
|
Thank you, HomerHorwitz, for a patch that changes login location handling
to use the sim UUID if it has already been stored.
|
|
Thank you, HomerHorwitz, for a patch that corrects and improves TP
to landmark and home position handling.
|
|
Thank you, gsky, for a patch that corrects the threading model
to use the multithreaded apartment in the grid servers and
region server.
|
|
* Looks like these weren't so unused after all - oops!
* Remove message from grid server config
|
|
|
|
service, adding a plain REST GET handler returning XML (no LLSD),
adding appropriate add handler calls to OpenSimBase and UserServer.
|
|
GetInventorySkeleton
|
|
the specific inter service class
|
|
services) into a separate assembly to parallel OpenSim.Region.Communications.OGS1
|
|
than inter grid
|
|
inventory server (see http://opensimulator.org/wiki/Security_vulnerability_brought_by_non-check_inventory_service)
|
|
the other service calls
* will post to mailing list about moving this shortly
|
|
Agent table code (INSERT / UPDATE, etc) now added to MSSQL provider.
|
|
support. As far as I know, the LLSD login method is currently only used by libsl based clients/bots. So could be useful to be able to disable this if a grid comes under a griefing attack from libsl bots.
|
|
And reverted CachedUserInfo back to revision 5262.
I don't think most of the inventory problems that people are reporting are due to these, but its easier to deal with one set of potential problems at a time, and I'm not going to get any time in the week to work on this anyway.
|
|
in the loginservice
|
|
time to look into the problems people are having.
|
|
|
|
The Login service should now read/create new inventory on the inventory server that is set in a users profile.
Also added "Add-InventoryHost" console command to add a support for a new server to a region.
So it would be good if someone could test this. Set up the grid as normal, but then also run extra inventory server on a different computer (well actually it just has to be on a different network hostname, so one using "http://localhost:8004" and one using "http://127.0.0.1:8005" should work) then you need to manually edit the user profile database to set the new servers url in a user's "userInventoryURI" field.
Then on a region server, use the Add-InventoryHost to add the new server url (always include the full url, including http, but don't add a final /)
Login with that account and see if the inventory works.
Of course these needs to be made more user friendly.
|
|
|
|
World->Region/Estate. Then on the Estate tab, at the lower right hand corner, clicking the 'Add' button and picking an avatar.
* It only persists across reboots for the mySQL datastore currently.
* Currently have stubs in the other datastores.
|
|
|
|
* You'll need to start-up the MessageingServer and set it up. It sets up like any of the other grid servers.
* All user presence data is kept in memory for speed, while the agent is online. That means if you shutdown the messaging server or the messaging server crashes, it forgets who's online/offline.
* Occasionally the region-cache will get stale if regions move around a lot. if it gets stale, run clear-cache on the messaging server console to clear the region cache.
|
|
style way over XMLRPC.
* Friend status updates are still only local, so you still won't know before instant messaging someone if they're online.
* The server each user is on and the user server must be updated or the instant message won't get to the destination.
|
|
related.
|
|
must remember to nant clean
* Hook all server startups into base opensim server startup method
|
