similar to: CentOS 7, nfs & autofs

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

I'm having a problem with automount (autofs) from a server running CentOS 5.4 to clients (example is CentOS 5.4). Client pulls automount maps from NIS. THIS particular server is also used for login so it is NIS bound as well (other servers are NOT). ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NIS Server Side... (content shortened)

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

Hi, I have a autofs configured to mount home dir from NFS. All user accounts lookup is done using LDAP. All is working fine with this setup. Now I need to create a local user account and have its home dir also on local system. So I added a new user account and changed auto.home as follows: test1 -rw,hard,intr /home/test1 * -rw,hard,intr nfs1:/export/users/& But this

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 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:

On 6/8/2017 11:03 AM, Fred Smith wrote: > 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. Automounting is now done through systemd. You just have to create two "unit files" to describe the mount. One holds the information for a

For those of you using CentOS 4, is anyone having trouble with autofs 4.1.3? I'm seeing (with 60second unmount timeout) what appears to be an apparent race condition where a script touches an automount directory at about (the same second according to logs) the same time the unmount is triggered, and the script then gets a read error. Sure, increasing the unmount timeout will reduce the

This is primarily an autofs issue, but I wanted to get the problem and the workaound into the Samba lists for reference. I use RHEL 5 and RHEL 6 these days, and take advantage of CIFS automounting with the built-in Samba pacakges. The problem still occurs with the more modern cifs-utils that's been separated out in more recent Samba 3.6.x and Samba 4 toolkits as well. I use a very simple

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,

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

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, We've been using autofs and LDAP automount maps for years now, and it has worked well. We run an environment that has CentOS, RHEL, Solaris and FreeBSD servers and clients. Historically, all our automount maps have looked like this: -vers=3 server:/export/home/& However, we're switching to NFSv4 and therefore we need to remove the -vers=3 flag. For CentOS 6.3, Solaris and

I haven't seen this on the linux-security list so I thought I'd forward it on for your review. It was pulled from Bugtraq by one of our sys admins. Dan _______________________________________________________________________________ Dan Yocum | Phone: (630) 840-8525 Computing Division OSS/FSS | Fax: (630) 840-6345 .~. L Fermi National

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

On Mon, 21 Aug 2017 14:52:40 +0200 Jeremy Guasco <jguasco+samba at lncsa.com> wrote: > Le 21/08/2017 à 14:15, Rowland Penny via samba a écrit : > > > > That's the correct way to do it (the wikipage was wrong, I have > > corrected this) > > > > Have you checked that the objectClasses are in AD ? > > > > ldbsearch --cross-ncs -H

Hello all This patch tries to remove a few bugs from smbmount. It would be nice to get some testing+feedback on this from others using smbmount and possibly get these things fixed for the next release of samba. It does the following: * Change lib/debug.c to allow changing your mind on being interactive. A second call to setup_logging should now replace the effects of a previous call. (hmm,

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>

Author: casper Repository: /hg/zfs-crypto/gate Revision: b8dc006ee63f520b5db5b6a94d1746a6518ff072 Log message: 6268481 unprivileged user calling umount on a autofs mountpoint hangs Files: update: usr/src/uts/common/fs/autofs/auto_vnops.c

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 |