-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi.

!M nxclient 1.3 and kNX does not support resume of sessions, but !M
nxclient 1.4 does. To workaround this freenx will autoresumes
connections fromk 1.3.0 and 1.3.2, but not 1.4.0. This works perfectly
with !M clinets, giving 1.3.x users the first availible session resumed,
and allows 1.4.0 users to choose what session to resume, if any.
However, kNX report itself as 1.4.0, and is thus not autoresumed, while
it still does not support the 1.4.0 resume feature.
You can fix this bug in thre ways. The best would be to add the resume
feature to knx, but if that's not feasible you can either modify kNX
sources so it present itself as 1.3.2, or set ENABLE_AUTORECONNECT="1"
in FreeNX node.conf, which will autoresume all clients, including !M
nxclient 1.4.0. The drawback of this is that !M nxclient 1.4.0 will
autoresume the first availible session instead of presenting a choise to
the user.

Hope this clarifies the issue.

Regards
- - Jonno


Sami A. Hassanein wrote:
> Hi
> 
> I am running 2 hosts, workstation and server. On each of them I have suse
> 9.2 and I want to connect through FreeNX from client to workstation.
> Qt: 3.3.3
> KDE: 3.3.0
> KNX: 0.1
> 
> On the workstation I use nxserver --start
> On client I use knx and I terminate this session with 'suspend'.
> 
> How can I restore this session. If I use knx --session <sessionid> there
> will be created a new session always.
> 
> Where can I find the correct sessionid?
> Is there something that I do wrongly?
> 
> --
> Thanks for any help
> Sami
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCVPU9OOpxqcksWu4RAvOJAJ44oZiH3QyhiwR2dcD+BIA/yGjBsQCgpXXr
1BWfr5RdMzp5EJpNn2RWN/g=
=QgCJ
-----END PGP SIGNATURE-----