similar to: CentOS 4 & autofs 4.1.3

I'm having an issue with autofs mounting cifs using kerberos, on machines joined to an S4 domain controller. Both hosts and S4 server are CentOS 6, and the DC is running samba-4.1.11 from sernet. Autofs is getting it's maps from LDAP from the DC. This part works fine, automount -m shows: Mount point: /share source(s): instance type(s): sss map: auto.share public |

Hi, after trying sshfs to mount a remote file system on a server with the result that sshfs will sooner or later get stuck and require a reboot of the client, I'm fed up with it and am looking for alternatives. So next I would like to use NFS over a VPN connection instead. To minimize the instances of the NFS mount getting stuck, it might be helpful to use autofs. What happens when the

On Wed, Aug 23, 2017 at 12:03:12PM -0700, Gordon Messmer wrote: > On 08/21/2017 07:23 PM, Fred Smith wrote: > >so, in my case, the USB drive contains an xfs filesystem. would I > >do something like this: > > > >in /etc/auto.master: > >backup /etc/auto.backup > > > >and in /etc/auto.backup > >backup -fstype=xfs,defaults,noauto,users

Hi, I'm using Autofs and LDAP for mounting my home directories via nfs. In general, everything seems to work fine. However, I have one small problem. If I reboot my server using autofs while my LDAP server is down, I get the following error message in my logs: automount[3358]: bind_ldap_anonymous: lookup(ldap): Unable to bind to the LDAP server: (default), error Can't contact LDAP

I have an issue with CentOS 6.2's autofs/automount. When I issue "service autofs start (or restart)" the automount daemon starts as expected, however, I am not able to access any of the exports nfs directories; but if I shutdown the automount daemon and start it by just issuing "/usr/sbin/automount", I am able to access all of the nfs directories. If the system reboots,

Was trying to use autofs on ubuntu and mounting a samba shared failed. Then, i came across a note that 'unless you need to authenticate to cifs' -- wish I could find the exact quote now. The point is autofs fails to mount a windows server share. I can mount the share using mount.cifs but it fails with autofs. So I just thought I would check to see if anyone has pointers on using autofs on

Hi all! I'm trying to set up autofs on my C7 netbook so I can automount a cifs share (actually two) from my NAS box, and because when I'm not at home I don't want it attempting to mount it. so I've read several howtos on it, including the one on the CentOS Wiki. but what I've got isn't working right, and I don't know why. I'm trying to follow the

Hi, Does setting the autofs timeout=0 create a permanent mount? What I'm trying to do is get the best of both world; 1) Have a persistent mount so that users can use autocompletion. 2) utilize the benefits of autofs so that when an NFS resource becomes unavailable, the system doesn't hang. I've tried a timeout of 0 but it doesn't seem to work.

Hi! Thanks to some of you I got autofs set up on my C7 netbook for mounting local cifs filesytems. Now I want to do something on my C7 desktop machine, that seems to me to be a little different, and I"m not sure how to do it. I have an external RAID1 box that attaches via USB. It is/will be nearly always /dev/sdc, but being USB I can't guarantee that it will always be found there.

One problem I have with custom CentOS 6 installation is that NIS auto.* maps are not available. According to boot.log, ypbind starts before autofs, but when I login to the machine, the maps are not available until I issue a service autofs restart. Any pointers on what to check?

On 08/30/2015 04:32 PM, Frank Cox wrote: > On Sun, 30 Aug 2015 16:20:21 -0500 > Robert Nichols wrote: > >> Once the system gets into this state, the only remedy is a forced >> power-off. What seems to be happening is that an NFS filesystem that >> auto-mounted over a WiFi connection cannot be unmounted because the >> WiFi connection is enabled only for my login

Hi all, I'm trying to setup this scenario on NFS and autofs on Centos 4.3: - useradd nfstest on an NFS server (192.168.1.247) - Setting up this NFS server /etc/exports: /home/nfstest 192.168.1.252/255.255.255.0(rw,sync,no_root_squash) - useradd nfstest on a client machine (192.168.1.252) - make sure that the uid and gid are the same on the server and the client - setting up

On Wed, Aug 23, 2017 at 01:59:23PM -0700, Gordon Messmer wrote: > On 08/23/2017 01:06 PM, Fred Smith wrote: > >so, the two lines saying: Key "syno-fredex" or key "syno-public" > >appear whenever I try to access one of those two filesystems. I AM NOT > >USING AUTOFS TO MANAGE THEM. > > > You're using autofs to manage /mnt, so any time that

Good day please excuse my delayed response. Thanks for the hint with the machine account. I will try this. I realised I can also manually refresh Kerberos tickets. I have the following: $ klist Valid starting Expires Service principal 02/12/2024 08:39:44 02/12/2024 18:39:44 krbtgt/CAMPUS renew until 02/13/2024 08:39:40 so this ticket is valid until 12. February 18:39.

On Tue, Feb 2, 2016 at 9:23 AM, <m.roth at 5-cent.us> wrote: > Dave Burns wrote: > > My NFS server is up and other clients can access x. One particular client > > can't. I tried to unmount the NFS share: > > > > [root at nfsclient ~]# umount -f /disk/x > > umount2: Device or resource busy > > umount.nfs: /disk/x: device is busy > > umount2:

Hi, I am still trying to figure out the best settings for Samba and Kerberos with autofs. My setup so far works good, users can log in on their computers using AD credentials, and they can access network shares with AD credentials as well. This works perfect. Also I notice that some Kerberos ticket is created upon user login, which allows the users to access a Samba share without entering the

We have about 800 CentOS 5.2 servers and our university. We use NFS being served from over 10 NetApp frames. We use autofs for to mount up our partitions. There have been times where we can't cd into the directory. It says the directory does not exist. On some servers it works but on others it does not. Typically we restart amd and autofs to resolve this issue. But sometimes it does not even

Hi, the last released autofs update for Centos 5 is version autofs-5.0.1-0.rc2.55.el5.1. On 2007-12-20 upstream released version autofs-5.0.1-0.rc2.55.el5.2. As several other updates were released in the meantime maybe the autofs update has been overlooked? Best regards, Bernd.

I am using autofs for a number of machines connecting nfs shares. All the mount and unmount log entries on the server are being saved to /var/log/messages currently. This is becoming a bit of a pain because as the number of hosts increase and various monitoring scripts check to be sure that they have access to the nfs shares it is filling up messages on the nfs server. I would like to continue

On Thu, Jun 08, 2017 at 04:02:05PM -0700, Kenneth Porter wrote: > Automounting is now done through systemd. In my use, we continue to use autofs for automounts of CIFS volumes, because as best I can tell, systemd doesn't support using the request-key infrastructure to use a user's kerberos ticket to set up the automount. -- Jonathan Billings <billings at negate.org>