Hi all,
for post-Baikal coding here the first proposal to get rid of (or
minimize) the lost .x2go/<session> directories:
Place file ,,profilename'' in the .x2go/<session-name> directory to
become able to relate between server and client.When connecting to an X2go server do the following:
o do everything from now in background, 2 minutes after the session has started o get a session list from the server o check local session directories in .x2go/ for matching sessions o for any session that is in R or S state on the server: keep the local session directory o for any other session directory on the client that contains a profilename file with the currently connected profilename in it: remove the local session directory as the session is obviously not valid any more on the server
On session profile renames: remove all cached .x2go/<session>
directories for the old session profile name.
Feedback!!!
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On 2011-07-29 10:39, Mike Gabriel wrote:
- Place file ,,profilename'' in the .x2go/<session-name> directory to become able to relate between server and client.
Why is this needed? I do think we must relate a session profile to a server, though. Especially when using a shared home, but a local sqlite database.
o do everything from now in background, 2 minutes after the session has started
This should be a very cheep operation (query db , compare, rm). I think there is no need to delay. ;)
Cheers Morty
-- Dipl.-Ing. Moritz 'Morty' Struebe (Wissenschaftlicher Mitarbeiter) Lehrstuhl für Informatik 4 (Verteilte Systeme und Betriebssysteme) Friedrich-Alexander-Universität Erlangen-Nürnberg Martensstr. 1 91058 Erlangen
Tel : +49 9131 85-25419 Fax : +49 9131 85-28732 eMail : struebe@informatik.uni-erlangen.de WWW : http://www4.informatik.uni-erlangen.de/~morty
Hi Morty,
On Fr 29 Jul 2011 10:55:27 CEST Moritz Struebe wrote:
On 2011-07-29 10:39, Mike Gabriel wrote:
- Place file ,,profilename'' in the .x2go/<session-name> directory to become able to relate between server and client.
Why is this needed? I do think we must relate a session profile to a server, though. Especially when using a shared home, but a local sqlite database.
Currently we do not know which .x2go/<session> dir belongs to what
session profile (=server) if the server-side session has terminated.
That is: if the server-side session has vanished, we do not know if an
.x2go/<session> is actually a terminated session on session profile A
or a still running session on session profile B.
We could also look for entries in session.log that inform about a
terminated session:
mike@mimino:~/.x2go$ grep -ri "session terminated" *
S-locadm-50-1311057154_stDGNOME_dp24/session.log:Session: Session
terminated at 'Tue Jul 19 08:33:13 2011'.
S-locadm-51-1311437782_stDGNOME_dp24/session.log:Session: Session
terminated at 'Sat Jul 23 16:49:39 2011'.
S-locadm-52-1309380386_stDGNOME_dp24/session.log:Session: Session
terminated at 'Wed Jun 29 21:42:50 2011'.
S-locadm-52-1311438419_stDGNOME_dp24/session.log:Session: Session
terminated at 'Sat Jul 23 17:06:20 2011'.
S-locadm-61-1311281243_stDGNOME_dp24/session.log:Session: Session
terminated at 'Sat Jul 23 16:43:56 2011'.
S-locadm-61-1311281243_stDGNOME_dp24/session.log:Session: Session
terminated at 'Sat Jul 23 17:14:09 2011'.
However, what I do not like about this last approach is: it is NX
specific. I would rather like some x2go specific method to grip here...
Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
On Fri, 2011-07-29 at 11:04 +0200, Mike Gabriel wrote:
Hi Morty,
On Fr 29 Jul 2011 10:55:27 CEST Moritz Struebe wrote:
On 2011-07-29 10:39, Mike Gabriel wrote:
- Place file ,,profilename'' in the .x2go/<session-name> directory to become able to relate between server and client.
Why is this needed? I do think we must relate a session profile to a server, though. Especially when using a shared home, but a local sqlite database.
Currently we do not know which .x2go/<session> dir belongs to what
session profile (=server) if the server-side session has terminated.
That is: if the server-side session has vanished, we do not know if an
.x2go/<session> is actually a terminated session on session profile A
or a still running session on session profile B.We could also look for entries in session.log that inform about a
terminated session:mike@mimino:~/.x2go$ grep -ri "session terminated" * S-locadm-50-1311057154_stDGNOME_dp24/session.log:Session: Session
terminated at 'Tue Jul 19 08:33:13 2011'. S-locadm-51-1311437782_stDGNOME_dp24/session.log:Session: Session
terminated at 'Sat Jul 23 16:49:39 2011'. S-locadm-52-1309380386_stDGNOME_dp24/session.log:Session: Session
terminated at 'Wed Jun 29 21:42:50 2011'. S-locadm-52-1311438419_stDGNOME_dp24/session.log:Session: Session
terminated at 'Sat Jul 23 17:06:20 2011'. S-locadm-61-1311281243_stDGNOME_dp24/session.log:Session: Session
terminated at 'Sat Jul 23 16:43:56 2011'. S-locadm-61-1311281243_stDGNOME_dp24/session.log:Session: Session
terminated at 'Sat Jul 23 17:14:09 2011'.However, what I do not like about this last approach is: it is NX
specific. I would rather like some x2go specific method to grip here...
<snip> I would also like to see it NX independent. I could see us integrating SPICE within a year - John
-
John A. Sullivan III -
Mike Gabriel -
Moritz Struebe