First off, this sounds like a bug. Considering the way you are explaining it, it sounds like an issue with the way variables are read/written from the ini files. I think that the applications.ini file should never need to be edited by the tango service, unless you are using the config.taf tool to build out a new application.
Because of that, you should be OK if you adjust the permissions on applications.ini to be read-only by the user that your tango service runs as. Robert From: WebDude [mailto:[email protected]] Sent: Monday, June 07, 2010 3:25 PM To: [email protected] Subject: RE: Witango-Talk: Muxed variable on a hard crash Witango 2000 Windows 2000 Fully patched There are actually 2 variables that hold the breadcrumb. It is configured like this... top/archive/<@VAR q>/<@VAR mc>/ Note, the whole path ends up in the ini file (Path=top/archive/history/creamy/). No crash event dump, just s restart. I will try changing the persistentrestart=false Witango version? OS & version? Name of variable that holds the breadcrumb nav? Does witangoevents.log report a crash event (a dump?) You can try editing Witango.ini, set persistentrestart=false and see if it continues with that setting. Robert From: WebDude [mailto:[email protected]] Sent: Friday, June 04, 2010 1:58 PM To: [email protected] Subject: Witango-Talk: Muxed variable on a hard crash Hey Everyone, I got a wierd thing happening... it has happened twice so far. When one of our servers crashes (i.e. a power outage), on reboot, everything comes up fine except for the applications.ini file. Typically, one of the settings is Path=/ But on a hard crash, the Path is changed to Path=top/archive/history/flavors/creamy/ After the hard crash, I go and change the ini file back to Path=/, stop Witango and restart it and everything is fine. What is wierd is that this path does not exist on the server, though it does exist as a user scoped variable that loads breadcrumb navigation on one of our sites. I searched everything on the server for this string of text, including the registry and cannot find it. I am wondering on a hard crash where Witango gets this value. Does anyone have any clue as to what is happening? No, the server is not hacked. It is only noticeable on one site in which I use an application scoped variable. It is the only place on this server in which an application scoped variable is used... and it's not even the same site as where the breadcrumb navigation is?!?!?! Wierd... ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
