One easy way to resolve your issues it to use different names for the export location and the mount location. Your export location is handled by fstab, whereas your mount location is handled by autofs. For example, your have server1 with /export_data1 and server2 with /export_data2 mounted via fstab. NFS + autofs will mount them as /data1 and /data2 on all the clients including the NFS servers. Does this work for you ?
On Sun, Jul 2, 2017 at 1:58 PM, Petros Triantafyllidis via FreeIPA-users < email@example.com> wrote: > Hi all, > I am very new to IPA and still a bit before going into production, so > apologies in advance. > > The plan is to have a number of servers that each one shares a space via > kerberized nfs4 to the others, which makes all of them NFS clients and > servers at the same time. On my attempt to setup automount globally via IdM > and sssd, I realized that when a machine is configured as nfs server, it > needs autofs.service to be stopped in order to access it's local shares > mounted via fstab. If I use /etc/auto.master to mount the local shares > instead of fstab, then autofs.service may (actually must) run and > everything works properly but, doing so, I don't have the advantage of one > central configuration location any more. > The preferred scenario for each server would be to mount its local shares > via fstab and the remote shares via sssd automount. Am I missing something? > > Thanks in advance, > Petros > > > > _______________________________________________ > FreeIPA-users mailing list -- firstname.lastname@example.org > To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org > >
_______________________________________________ FreeIPA-users mailing list -- email@example.com To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org