Privilege of user account

Forum / NoMachine Terminal Server Products / Privilege of user account

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • August 31, 2020 at 14:08 #29257
    Aubert887
    Participant

    How to disable a NX user to shutdown a computer. In my case when a user open a session xfce4,  It could shutdown the computer using the terminal. How can I avoid this isssue?

    After that, when my session goes on standby mode, the Xsreensaver give this message: Xscreensaver Authentification failed

     

    Cordially,

    Thanx

    Attachments:

    1. bizarre.png

    September 1, 2020 at 13:57 #29281
    graywolf
    Participant

    The first issue looks related to Xfce configuration.

    About the screensaver, please tell me the Linux distro in use.

    Is the Xfce session running on a NoMachine virtual desktop or on a physical display?

    September 1, 2020 at 14:21 #29282
    Aubert887
    Participant

    I use Red Hat Linux (7.7). xfce4-session runing on NoMMachine terminal server Node. I have build a multi node. My broker turn on NoMachine Enterprise Terminal Server and my host turn with NoMachine Terminal Server Node. I use url web.

     

    September 8, 2020 at 14:06 #29393
    hawk
    Participant

    Hello,
    NoMachine do not provide feature to block commands. You can do this by configuring sudoers file for example.
    http://www.tecmint.com/disable-shutdown-and-reboot-commands-in-linux/

    About xscreenserver problem we are unable to reproduce the problem. Please check if changing DefaultDesktopCommand key value in /usr/NX/etc/node.cfg (on server side) from “/usr/bin/startxfce4” to “dbus-launch /usr/bin/startxfce4” will fix the problem. You need to have root permissions to change values in NoMachine configuration files.

    If this will not help some logs may be helpful. Please run command sudo grep xscreensaver /var/log/secure* and send us output to forum[at]nomachine[dot]com, referencing the topic as subject.

    September 25, 2020 at 16:20 #29628
    Aubert887
    Participant

    Sep 22 09:41:25 xxxxxxxxx xscreensaver: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth
    Sep 22 09:41:25 xxxxxxxxx xscreensaver[6610]: FAILED LOGIN 1 ON DISPLAY “:1001.0”, FOR “xxxxxx”
    Sep 22 09:41:30 xxxxxxxxx xscreensaver[6610]: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth
    Sep 22 09:41:30 xxxxxxxxx xscreensaver[6610]: FAILED LOGIN 2 ON DISPLAY “:1001.0”, FOR “xxxxxx”
    Sep 22 09:41:47 xxxxxxxxx xscreensaver[6610]: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth
    Sep 22 09:41:47 xxxxxxxxx xscreensaver[6610]: FAILED LOGIN 3 ON DISPLAY “:1001.0”, FOR “xxxxxxx”
    Sep 22 09:42:03 xxxxxxxxx xscreensaver[6610]: PAM _pam_load_conf_file: unable to open /etc/pam.d/system-auth
    Sep 22 09:42:03 xxxxxxxxx xscreensaver[6610]: FAILED LOGIN 4 ON DISPLAY “:1001.0”, FOR “xxxxxxx”

    November 16, 2020 at 13:56 #30394
    Britgirl
    Keymaster

    The excerpt you posted seems to show it is not a NoMachine problem at all.

  • Author
    Posts
Viewing 6 posts - 1 through 6 (of 6 total)

This topic was marked as solved, you can't post.