zaq

[zaq]

Value of AvailableSessionTypes entry is reseting during update. This is list of keys which are re-set during every update:
– server.cfg

ClientConnectionMethods
AvailableSessionTypes

– node.cfg

Most of those keys keeps the paths to system tools. The paths are refreshed during every update/upgrade.

CommandFuser
CommandLsof
CommandXdpyInfo
CommandXmodmap
CommandXkbComp
CUPSBinPath
CUPSSbinPath
CUPSBackendPath
EnableCUPSSupport 1 (checks if CUPS is available if YES, set to “1”)
ClientConnectionMethods
AudioInterface (checks which audio tool is available)
CommandStartPulseAudio
EnableSMBFSSupport
AvailableSessionTypes

Your old *.cfg file has changed name:
server.cfg -> server.cfg.backup
node.cfg -> node.cfg.backup
You can easly restore your old *cfg file.

If any entry during update is duplicated it’s a bug. Could you send more information about the case. A *cfg file with double entries will
be helpful and also /usr/NX/var/log/nxinstall.log and the /usr/NX/var/log/nxupdate.log files from the server side installation.

These files you can attach here or send to issues[at]nomachine[dot]com.

[zaq]

Hi,

After the update all services should be working. The update procedure updates the configuration files (*.cfg)
only for adding new configuration keys. Your settings in the *.cfg files shouldn’t be changed, likewise license
files (*.lic) aren’t overwritten and files in  NX/etc/keys/ remain the same.

No special package. As explained above, the update procedure is intended to preserve current configurations and settings.
If this is not the case, ie. you have found your configuration or keys changed, please tell us what these are.

Logs would also be useful which you can attach here or send to issues[at]nomachine[dot]com

We will need the /usr/NX/var/log/nxinstall.log and the /usr/NX/var/log/nxupdate.log  files from the server side installation.

[Author]

Posts