CentOS

Hi all,

Thank you for your clarification.

As I understand, every process that a user runs over VNC inherits the permission set when the VNC session is started. That is why permissions of a process are not updated while the VNC process is up and running.

Hi,

I encountered this issue when I used usermod command to add a user to an existing group.

I noticed that when the user and group permissions of a certain user are updated, the new settings do not apply for the current VNC session. Hence, it is required to restart the VNC session.

Is there a way to apply the new settings without restarting the VNC session?

I think it is overwritten when I restart the service as everything looks normal to me.

I attached the log file for your information.

Hi, I get the following: journalctl -u vncserver@\:38.service -- Logs begin at Sun 2024-01-28 20:20:37 +03, end at Mon 2024-01-29 12:47:29 +03. -- Jan 28 20:20:43 centos7-server systemd[1]: Starting Remote desktop service (VNC)... Jan 28 20:20:44 centos7-server systemd[1]: Started Remote desktop ser...

I noticed that one of the users were unable to access the machine via VNC after starting the machine. When I check the service status, I have the following message: systemctl status vncserver@\:38.service ● vncserver@:38.service - Remote desktop service (VNC) Loaded: loaded (/etc/systemd/system/vncs...

You could run that systemctl daemon-reload as the output suggests. The firewalld.service seems to be masked, so everything should be ok. I do agree with Trevor that complete removal of FirewallD is the most clean option. The removal of firewall* on CentOS 7 system probably removes: firewall-applet,...

Is there any side effect of leaving the state of the firewalld.service as it is? Do show output of systemctl status firewalld # systemctl status firewalld ● firewalld.service Loaded: masked (/dev/null; bad) Active: inactive (dead) Sep 13 22:24:17 centos7-server systemd[1]: Cannot add dependency job...

The postinstall script of package 'iptables-services' does do some "systemctl preset". I'd guess that those "presets" change what services can run. (Plain "yum install" does not stop firewalld; I guess the effect would show on next restart.) One can enforce that an installed service does cannot run...

I noticed that after installing iptables.service, returns

FirewallD is not running

Is it an expected thing?