SYSLOGINS (OpenInsight 32-Bit)
At 23 MAY 2006 09:33:48AM Colin Rule wrote:
Some users are not exiting correctly and using up users.
They do tend to clear, but I would like to manage SYSLOGINS better.
Is is OK to clear or delete items from this file, a) without causing problems and b) within the end user licence.
I dont want the user to have to restart the LH service or anything like that.
Suggestions please on how best to ensure all users can access even if they are doing things wrong.
Also, when I look at REV30101 in Notepad, it has other info which does not appear when you look at it in System Editor, I am wondering why?
Thanks
Colin
At 23 MAY 2006 09:51AM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
You'll need to remove SYSLOGINS_MFS from the file handle but then you'll have no problems. SYSLOGINS is not used for licensing it is provided as a convenience for you to see who is logged in. The MFS removes the process id from the row id under normal circumstances to keep backwards compatibility.
World leaders in all things RevSoft
At 23 MAY 2006 10:24AM Gerald Lovel wrote:
Colin,
I am not sure what question you are asking. If users are not exiting "correctly," are they exiting OI or not? Are you looking for a way to detect user interface idle, so that users can be logged out automatically When the application remains open on their system? Some user would have to be logged in to manage SYSLOGINS per your question. But if idle users are being logged out, who would be left to manage SYSLOGINS?
My thinking is that SYSLOGINS should be managed by OI internals without developer/application mucking. I understand that this would not account for workstation reboots, however, where OI is murdered instead of expiring normally. So what is happening? Are your users instinctual killers?
Gerald
At 23 MAY 2006 04:23PM [url=http://www.sprezzatura.com]The Sprezzatura Group[/url] wrote:
Colin,
If you want to make sure SYSLOGINS is clean just perform a SELECT against the table and it will check for and remove any ghost entries (I wouldn't try deleting records from this table yourself - it's system maintained for a reason ;)
If you run a select and the records aren't cleared that you know should be the chances are the user has exited but locks are still held. Deleting records from SYSLOGINS won't release them - it's another issue entirely..
What other information are you seeing in files? There is a table header section to LK files before records start…
World leaders in all things RevSoft