[FreeNX-kNX] FreeNX, NX Web Companion, sessions closing

jhonyl jhonyl at netscape.net
Sat Nov 1 16:46:53 UTC 2008



Hi,

There has been a few post of similar purpose lately here in the mailing list. Here is a quote of few:

----------------

Hi,

In your .nxs file you can add the option:

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

or at least change it from true to false and write protect the .nxs file. Then 
at every NX Strat of this session you will get shown all your running sessions 
to resume and the possibility to click new.

Kind Regards,
Florian


---------------------------

and:
----------
On Fri, 31 Oct 2008 14:50:24 +0000
"Steven Maddox \(Cyorxamp\)" <s.maddox at cyorxamp.info> wrote:

> Hi Nico,
> 
> Thanks for this...
> 
> Now just got to solve how people can be logged into running only 
> 'firefox -no-remote' and not anything else when they connect... also if 
> you've got say 20 people all auto-connecting as 'test' user... won't I 
> need to put something in place to make sure they all get new 
> screens/sessions and not try to resume any existing ones?  (don't want 
> other guests seeing what a previous guest did).
> 

If you look in the node.conf file, you could e.g. DISABLE_PERSISTENT_SESSION="all", 
this would result in that one can't disconnect a session (remember to disable 
the corresponding ENABLE_.... settings, as all are enabled by default). If you 
name the sessions in the clients differently, you should be able to login as the 
same user, but each in different sessions.

I would also advise you to look at the great addition from Fabian called 
'nxacl', this should prove helpful for your purposes.
If you end up using 'nxacl', please share the solutions on the wiki, as Fabian 
requested as it would be helpful to others.

It would be nice if you keep us updated on your progress, as I think others 
would like to have a similar setup :-)

Regards,
Terje


---------------------



-----Original Message-----
From: Kurt Godric <kgodric at hotmail.com>
To: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
Sent: Sat, 1 Nov 2008 4:16 am
Subject: [FreeNX-kNX] FreeNX, NX Web Companion, sessions closing



I am using the NX web companion and it works well, on one machine.  But if I log in from another machine, the session on the first machine closes.  I need to be able to log in as the same user on multiple machines concurrently, but not share the same desktop.  Each time I log in I need to get a new desktop.



Thanks

Want to do more with Windows Live? Learn “10 hidden secrets” from Jamie. Learn Now = 


________________________________________________________________
    Were you helped on this list with your FreeNX problem?
   Then please write up the solution in the FreeNX Wiki/FAQ:
http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ
 
        Don't forget to check the NX Knowledge Base:
                http://www.nomachine.com/kb/ 
________________________________________________________________
      FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
     https://mail.kde.org/mailman/listinfo/freenx-knx
_______________________________________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20081101/f5bedc41/attachment.html>


More information about the FreeNX-kNX mailing list