Currently, if more than one sga-guard session is initiated to the same (user,machine), each session overrides the unique symbolic link used for communication. When that latest session dies, the older session does not become active again.
We should perhaps use a directory of sockets, and sga-ssh will use the latest one (based on timestamp)
Currently, if more than one sga-guard session is initiated to the same (user,machine), each session overrides the unique symbolic link used for communication. When that latest session dies, the older session does not become active again. We should perhaps use a directory of sockets, and sga-ssh will use the latest one (based on timestamp)