Two kinds of errors caused by root / lack of execution permission x

The Linux root directory lacks X permissions, resulting in two errors:
Execute the SystemCTL command as root to report permission related issues
[[email protected] ~]# systemctl stop hps-manager
* (pkttyagent:10364): WARNING *: Unable to register authentication agent: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PolicyKit1 was not provided by any .service files
Error registering authentication agent: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.PolicyKit1 was not provided by any .service files (g-dbus-error-quark, 2)
Switch from root to normal user and report an error:
[[email protected] ~]# useradd aihps
[[email protected] ~]# su – aihps
su: warning: cannot change directory to /home/aihps: Permission denied
su: failed to execute /bin/bash: Permission denied
The solution
Directory
Device: fd01h/64769d Inode: 2 Links: 23
Access: (0600/ DRW –) Uid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root) Gid: (0/root)
Access: 2016-05-30 09:54:45.692000000 +0800
Modify: 204000000 +0800
Change: 2016-05-25 15:41:46.204000000 +0800
Birth: –
problem, the permissions here are wrong, the loss of X permissions caused.
[[email protected] ~]#chmod 755/
modified, the problem goes away.
The operation that causes the above problem:
the first type, chmod 666 /, can cause.
or
the second, chmod 700 /lib/ ld-xxx. so, can also cause su to fail.
if you’re interested, try it out for yourself.
/the loss of permissions has the same effect on all daemons running on their own user identities.
Refer to the article: http://blog.itpub.net/9606200/viewspace-745674/


Read More: