Automount/autofs

From DISI
Revision as of 00:49, 8 August 2018 by Benrwong (talk | contribs) (created automount page)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

I am testing automount/autofs on backstreetboys.desktop.ucsf.bkslab.org. /etc/fstab causes us problems when one of the NFS servers are down. I'd like to move us to autofs mounts for future machines. There have been autofs issues in the past. For now, I'll use this on the desktops and see how they fare.

Issues

Aug 07 17:47:02 backstreetboys.desktop.ucsf.bkslab.org systemd[1]: Unit autofs.service entered failed state. Aug 07 17:47:02 backstreetboys.desktop.ucsf.bkslab.org systemd[1]: autofs.service failed. Aug 07 17:47:02 backstreetboys.desktop.ucsf.bkslab.org dbus[1016]: [system] Activating service name='org.fedoraproject.Setroubleshootd' (using servicehelper) Aug 07 17:47:02 backstreetboys.desktop.ucsf.bkslab.org polkitd[991]: Unregistered Authentication Agent for unix-process:4788:9276046 (system bus name :1.1679, object path /org/freedesktop/PolicyKit1/Authenticati Aug 07 17:47:03 backstreetboys.desktop.ucsf.bkslab.org dbus[1016]: [system] Successfully activated service 'org.fedoraproject.Setroubleshootd' Aug 07 17:47:03 backstreetboys.desktop.ucsf.bkslab.org setroubleshoot[4805]: SELinux is preventing /usr/sbin/automount from 'read, write' accesses on the file autofs-running. For complete SELinux messages run: s Aug 07 17:47:03 backstreetboys.desktop.ucsf.bkslab.org python[4805]: SELinux is preventing /usr/sbin/automount from 'read, write' accesses on the file autofs-running.

                                                                    *****  Plugin catchall (100. confidence) suggests   **************************
                                                                    
                                                                    If you believe that automount should be allowed read write access on the autofs-running file by default.
                                                                    Then you should report this as a bug.
                                                                    You can generate a local policy module to allow this access.
                                                                    Do
                                                                    allow this access for now by executing:
                                                                    # ausearch -c 'automount' --raw | audit2allow -M my-automount
                                                                    # semodule -i my-automount.pp