06-26-2015 02:04 PM
I think your best bet is to parse the object spawner logs, which will show you the connections to SAS workspace servers from EG (APPNAME=SAS Enterprise Guide), the user, and the process ID of the sas.exe process. For example:
2015-06-26T13:49:22,799 INFO  :cassmi@CARYNT - New client connection (204) accepted from server port 8591 for user cassmi@CARYNT. Encryption level is Credentials using encryption algorithm SASProprietary. Peer IP address and port are [::ffff:10.40.13.23]:11997 for APPNAME=SAS Enterprise Guide.
2015-06-26T13:49:23,142 INFO  :cassmi@CARYNT - Created process 19952 using credentials cassmi@CARYNT (child id 93).
2015-06-26T13:49:23,158 INFO  YSTEM@UITSRV04 - New out call client connection (205) for launched server (child 93). Peer IP address and port are [::ffff:10.121.18.73]:57832.
2015-06-26T13:49:23,158 INFO  YSTEM@UITSRV04 - Launched process 19952 (child id 93) is now running as process 17908.
2015-06-26T13:49:23,158 INFO  YSTEM@UITSRV04 - Client connection 204 for user cassmi@CARYNT closed.
2015-06-26T14:01:34,302 INFO  YSTEM@UITSRV04 - Client connection 205 for user cassmi@CARYNT closed.
2015-06-26T14:01:34,333 INFO  YSTEM@UITSRV04 - Process 17908 (originally 19952) for user cassmi@CARYNT (child id 93) has ended.
06-27-2015 03:21 AM
Thanks for your answer. I tried but there are some difficulties for finding the users logged in SAS EG.
I tried for multiple logs but can find only one message for SAS EG,so I am still unable to find the users.
I have following settings in the config file : logconfig.xml
<!-- Application message logger -->
Should I change anything to trace the users ?
I found following on the internet :
To increase the logging level for multiple spawner sessions :
Any recommendation from you?
06-27-2015 04:27 AM
Analyzing the logs will show what has happened in the past.
Doing analyses on running processes using the os commands like PS will show you what is happening now.
06-27-2015 05:26 AM
For the past, analyze the spawner log(s). For current state, ps -ef (on UNIX systems) will give you a list of all running processes; since workspace server sessions have a very distinct commandline, a proper grep will sort out the WS processes.