[FreeNX-kNX] NXServer inside of VServer?

[Martin Honermeyer]

Hello,

I am trying to get an NXServer running inside a Linux VServer
(www.linux-vserver.org). It works as far as this: KDE is starting, then the
splash screen says "initializing system devices" and pow! the session just
closes. It seems not to happen exactly at this point, but after the session
is running for a few seconds. No errors in the nxserver log, no .xsession
file in the user home (it should be there??).

As the capabilities inside the VServer are very restricted, I need some
advice from the NX devs about which system capabilities are needed in order
to get an NXserver running. A list is at
http://savannah.nongnu.org/cgi-bin/viewcvs/util-vserver/util-vserver/lib/bcaps-v13.c?rev=HEAD .


I am using the newest FreeNX 0.4.1 and the free NXServer components 1.5.0
r3. The problem was the same with FreeNX 0.2.8 and NXServer components
1.4.0.

If there are direct suggestions for a solution, at least I'd like to know
how to get some more verbose log output! NX_LOG_LEVEL=7 doesn't tell much:

...
NX> 1000 NXNODE - Version 1.4.0-04-CVS OS (GPL)
NX> 700 Session id: nx32-1004-A2499FCF6F24DE826CBD8940338E63D3
NX> 705 Session display: 1004
NX> 703 Session type: unix-kde
NX> 701 Proxy cookie: a9588103ea86b8550176359e4255a222
NX> 702 Proxy IP: 210.95.48.249
NX> 706 Agent cookie: bd1745d567d62cf63fbdbbaee2ecdcb5
NX> 704 Session cache: unix-kde
NX> 707 SSL tunneling: 0
NX> 710 Session status: running
NX> 1002 Commit
NX> 1006 Session status: running
NX> 105 bye
Bye
NX> 999 Bye
NX> 1001 Bye.
NX> 105 quit
NX> 1009 Session status: terminating
NX> 1006 Session status: closed


(Btw, SSL encryption doesn't work at all. The client times out at
"Negotiating link parameters".


Thanks for any help. It would be REALLY great to have this running!


Greetz,
Martin