@galvez_65 sorry I was looking at the server.cfg.sample
file not the server-fedora.cfg.sample
file in nxserver.tar.gz
. The config file is being edited correctly and is installed on my system with both StartNXDaemon Manual
and EnableFirewallConfirguration 0
set.
However, the nxserver.service
is still running and enabled after installing the package. I'm suspecting it's a problem with the upstream script nxserver
not repsecting it's own configuration rules. If someone else can confirm this is true, I'd just give up on offering PKGBUILD options and just have the package scream "REMOTE DESKTOP ACCESS IS ENABLED FOR YOUR MACHINE" as loud as possible.
Pinned Comments
runnytu commented on 2021-02-20 13:44 (UTC)
Since nomachine 7.1.3-2 the default behavior of the package is StartNXDaemon Manual and FirewallConfiguration 0 on a new installation, if you want to change this, you need to modify PKGBUILD build options with your desire behavior:
BUILD OPTIONS
Set to y to enable nomachine service autostart
_autoservice=n
Set to y to enable firewall autorules
_autofirewall=n
END BUILD OPTIONS