Hello. Symptom: user inserts a smart card, and gets a login screen instead of his running session; however session is still there on the server (ps command shows the processes). When this happens, utsession -p finds two sessions under the same token id. ... Payflex.500a457700130100 ??? hbd 25 Payflex.500a457700130100 ??? ??? 21 ... Attempt to kill session by display number (21 in this case) answers that session does not exist.
This happens sometimes - not too often, but enough to make it annoying. I failed to find any correlation between this and some user actions. What could be the reason of such behaviour? My installation is somewhat modified in scripts part, however AFAIK connection to running session is done in utauthd internally... Are any scripts affected when decision is made either to create a new session or to attach to existing one? I'm currently running 3.1beta, but I've seen the same also under 3.0 _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
