nxserver-freenx does not install an env.d entry e.g. 50nxserver: PATH=/usr/NX/bin ROOTPATH=/usr/NX/bin LDPATH=/usr/NX/lib CONFIG_PROTECT=/usr/NX/etc This means on a clean system and without nxclient (i.e. USE=-commercial) env.d entries for NX locations are not installed. nxserver-freenx should install /etc/env.d/50nxserver, same as other nxserver ebuilds.
Hi Ed I'm one of the FreeNX developers, and I can assure you that on a clean system and without nxclient (i.e. USE=-commercial) there is no need of any env.d entries! FreeNX sets LD_LIBRARY_PATH localy (so it won't affect other programs, which has been reported to have negative impact on other programs), thus no need for LDPATH. Neither does freeNX requires the nx binaries to be in path. There is no reasson for PATH, and the only reason for ROOTPATH would be if you use passdb (optinaly instead of using pam authentification). If so you'll have to run "/usr/NX/nxserver --adduser" instead of "nxserver --adduser" once in a while, which imho is no big deal. Neither is CONFIG_PROTECT nessesary as no files in /usr/NX/etc is overwritten during install (in 0.3.x there is node.conf.sample, but that's no harm in overriding it, as it is in node.conf you make any configuration changes). The FreeNX team has put a great effort in making sure that no system-wide environment changes (such as PATH or LD_LIBRARY_PATH) has to me made for it to work, in contrast to the NoMachine commercial nxserver, that requires changes to both PATH and LD_LIBRARY_PATH. This bug is invalid, and should be marked such. Regards - Jonno (jonno_at_users.berlios.de)
OK.
