Description of problem: freenx-server is improperly installed by the package maintainer. Version-Release number of selected component (if applicable): NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: not detected) How reproducible: yum install freenx-server Steps to Reproduce: 1. 2. 3. Actual results: Installs /etc/nxserver files with the following permissions: root@shiva nxserver]# ls -la total 64 drwxr-xr-x 2 nx root 4096 Oct 20 21:19 . drwxr-xr-x. 260 root root 20480 Nov 7 13:40 .. -rw------- 1 root root 668 Oct 20 21:19 client.id_dsa.key -rw-r--r-- 1 nx root 22608 Jun 17 05:59 node.conf -rw------- 1 root root 600 Oct 20 21:19 server.id_dsa.pub.key -rw------- 1 root root 672 Oct 20 21:19 users.id_dsa -rw-r--r-- 1 root root 600 Oct 20 21:19 users.id_dsa.pub Expected results: The /etc/nxserver directory files should be as follows: root@shiva nxserver]# ls -la total 64 drwxr-xr-x 2 nx root 4096 Oct 20 21:19 . drwxr-xr-x. 260 root root 20480 Nov 7 13:40 .. -rw------- 1 root root 668 Oct 20 21:19 client.id_dsa.key -rw-r--r-- 1 nx root 22608 Jun 17 05:59 node.conf -rw------- 1 nx root 600 Oct 20 21:19 server.id_dsa.pub.key -rw------- 1 nx root 672 Oct 20 21:19 users.id_dsa -rw-r--r-- 1 nx root 600 Oct 20 21:19 users.id_dsa.pub Additional info: To correct this I rebuilt the rpm post install script to include the command [root@shiva nxserver]# chown nx:root /etc/nxserver/* PS: The package maintaining for Fedora is steadily going to the dogs. Nobody is testing anything, or even making corrections to the packages in the bugs reports after we the public change them. I mean how hard is it to repackage simple crap like this? If Redhat doesn't want to be bothered, then create a way for the public to recycle the packages back into the production storage for public download. The open source community is more than willing to fix packaging problems.
You're supposed to run "nxsetup" after installing the package, that'll fix the permissions and do other necessary things for the server to work. If you must post rants like the "PS" part, I suggest directing them to some mailing lists instead of random bugs. But then again doing some homework before posting them would not hurt... not sure what you were trying to accomplish by flaming random volunteer package maintainers without giving them a chance to even comment on the issue you're having, let alone fix something (no fix needed in this case though)...