[FreeNX-kNX] Howto avoid free-nx to always resume a running session

Florian.Schmidt3 at infineon.com Florian.Schmidt3 at infineon.com
Mon Feb 18 07:16:17 UTC 2008


in your connection file .nxs you need the following line:

<option key="Automatic reconnect" value="false" />

Make sure that your .nxs is write protected or this setting is overwritten by the server default.
On serversite this should be:


Hope this helps!

Kind regards,

Dipl.Ing.(FH), Florian, Schmidt

Infineon Technologies IT-Services GmbH
LSF Mgmt, RD-Linux Admin
Tel.: +43 (0) 51777 4216
florian.schmidt3 at infineon.com

Lakeside B05
9020 Klagenfurt, Austria

Firmenbuch: LG Klagenfurt, FN 246787y

VISIT US AT: http://www.infineon.com/austria

-----Original Message-----
From: Gregory Carter [mailto:gcarter at aesgi.com]
Sent: Friday, February 15, 2008 8:57 PM
To: User Support for FreeNX Server and kNX Client
Subject: Re: [FreeNX-kNX] Howto avoid free-nx to always resume a running session

I am not so sure this will work.

KDE 3.x I do not believe has any sort of write locks for its current session information.

I mean, for example, in the case of forwarding samba and printer requests, there is currently I do not believe a way to tell which session from which, should get what forward.


Stefan Bauer wrote:
> Dear Users,
> i just read through the available manuals but did not find a resonable
> solution for this. i want to run more than one session at the same
> time and dont want that if i start another session with the same user,
> that the session which is already running get resumed by the new
> session request.
> Any help is greatly appreciated
> regards

     Were you helped on this list with your FreeNX problem?
    Then please write up the solution in the FreeNX Wiki/FAQ:
         Don't forget to check the NX Knowledge Base:

       FreeNX-kNX mailing list --- FreeNX-kNX at kde.org

More information about the FreeNX-kNX mailing list