Description of problem:
The nxsetup script fails.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. cd /usr/share/doc/freenx-0.7.0
2. run ./nxsetup
After answer the question about the key, the script fails with:
which: no nxloadconfig in
./nxsetup: line 130: .: filename argument required
.: usage: . filename [arguments]
Setting up ...mkdir: missing operand
Try `mkdir --help' for more information.
getting freenx to work
It was my experience that you don't need to run nxsetup to get freenx working.
Basically install, set up the config file, restart sshd, import the key to your
client, and you're in.
Hm, but in the doc directory there are no doc how to setup the config files.
nxsetup is for installing from the sources, e.g. it would conflict with the
files from the rpm. If something from nxsetup is missing in the packages we
should try to add it if possible.
Frank, could you list what configuration nxsetup would perform for you that the
current packages don't? Note that rpm does nto have an interactive mode by
design, so no site specific configuration that requires interaction with the
user can be done on a package level.
As an workaround I have installed the rpm packages from http://www.nomachine.com.
This works, but it have an total different config file structure. Because I need
an fast solution for it. When there are better documentation how to config the
freenx package than I can try it again. An simple yum install freenx are to
less, because not nxclient can connect.
Well, this is not a bug, there is no open source GUI to travel you through the
config file setup yet, nxsetup also just does some basic setup.