Multisession CS - Log off

[bluesfannoz]

Does anyone know how to logoff a client server session when you have MULTISESSION implemented. Many users are no longer prompted for their login and password to get in because it remembers their login until we kill brlistener and restart it. We had to implement MULTISESSION to get around a pdf bug on the mac, so now I need the capability to exit all sessions with a command. Anybody found anything?

Steve

[gordon]

The command to log off of a MULTISESSION session is SYSTEM LOGOFF.

Additionally, Windows occasionally begins reporting old sessions as active when logging on, even though the task manager shows no such sessions. When this happens, BR has no way to detect they are invalid and reassigns the WSID of the inactive sessions. This can be frustrating because BR gives priority to MULTISESSION assignments. It has to if it is to avoid the requirement of relogging in for subsequent sessions.

The way to clear the faulty Windows condition is to run the BRserver in standard mode on the failing client machine and then issue a SYSTEM LOGOFF. If SYSTEM LOGOFF is issued in in non-client/server mode BR clears the faulty entries in the Windows registry. This fix was put into br431ce (and greater) in the Dan directory.

[bluesfannoz]

Thanks for the info. I am primarily having this issue on the MAC because that is the only platform I have enabled multisession. Unfortunately this works but causes another issue. The brserver session closes on the server, but the brclient session on the client does not. It attempts what appears to be a connection to a nonexistent server and eventually comes up with an error of timeout waiting for connection. This is on 4.20o. Have no plans to upgrade any higher than 4.20o so if there is no further solution for this. I will attempt to find a workaround as this does successfully remove the sessions so the next time they go to logon it does prompt them for login and password.

[bluesfannoz]

I have come up with a solution for my problem for those interested:

I wrote this little logoff program that executes a script I wrote: I called my script 'killbrclient' and placed it in the /usr/bin folder with execute permissions

Script:
sleep .5
killall "brclient"


br program called logoff
10 execute "sys -@ killbrclient&"
20 execute "sys logoff"

This fires the killbrclient script as a background process, waiting .5 seconds to fire so the 'sys logoff' has a chance to fire shutting down and clearing the session. Then kills all occurrences of brclient running locally on the machine.

In my testing this cleared the multisession so the user will be prompted for his password on the next run of brclient and also kills the brclient session that was being left running after the 'sys logoff' was executed.

[GomezL]

This is BR 4.30 only, but ...

EXECUTE "Config CLIENT_SERVER RECONNECT_AFTER=10 RECONNECT_TIME=10
SYS Logoff


This sets the "Reconnect to 10 seconds, and then shuts down". As you mentioned, this should allow enough time to shutdown, but if not, the server shuts itself down.

PS: Are you certain that removing Multisession from the brlistener.conf doesn't work? (That should prompt the user for a password every time).

[bluesfannoz]

Removing MULTISESSION from the brlistener.conf does make them be prompted every time.

I had to implement MULTISESSION to workaround the MAC PDF memory leak issue I have mentioned in the past. I no longer have crashes after generating 50 or so PDF's when I create them in a second session fired when I want to generate the PDF. The memory leak would build until the client was exceeding the maximum amount allowed the workstation so it would crash. By firing a session to generated the PDF, that memory is released when each session completes, so I avoid the memory issue.