Forum Replies Created
XDM is supported but unfortunately at the moment that is a problem affecting the functionality,
described here https://www.nomachine.com/TR11K04020.
Server administrators can also add XDM login as a mandatory login method for specific groups of users.
In the meanwhile we are also investigating how the functionality can be improved, for example
to better integrate with the host environment.
Regarding Xwillings, as far as we know, this file is only used by XDM, while we would like to
offer a wider range of choices.
We believe that (once the bug will be fixed) the ability of the administrator to set the XDM login
command on the server will give people the best flexibility and adapt to most setups.
When the user runs a virtual desktop session, the server creates a new desktop.
This desktop is listed in the session list (displayed by ‘nxserver –list’)
and corresponds to the entry with the actual DISPLAY. At the same time,
the server adds the user’s connection to the session list: this is the
entry with the IP of the connected client.
There are actually 2 node instances. One is the display session itself,
the other is the user session connecting to that display.
The connection entry is present until the user closes (disconnects) the
session. If the user makes logout (i.e. terminates the session), both
desktop and connection entries are removed from the session list
and disappear from the ‘nxserver –list’ output.
It seems your perseverance helped us to find a bug 🙂
We have just edited AR10K00710 to provide instructions for
launching Xvfb as unprivileged user, we made additional
tests and we found some machines where running Xvfb as root
prevents NoMachine to be able to connect to the X server.
So please use:
‘Xvfb :0 -auth /var/run/Xvfb-0.auth -screen 0 1024x768x24 &’ instead.
Be sure that your run Xvfb as the same user who starts the dekstop
environment, otherwise the desktop will be not available.
We have opened a trouble report on that topic:
- This reply was modified 7 years ago by reza.