similar to: smbmount, winbind and autofs

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,

I am having some problems when I have a Win95 share mounted using smbmount. In some directories not all the directory entries are showing up for an ls. I can traverse the directories if I know what they are. I am running Debian Linux 2.0(libc6) with kernel 2.0.34 and samba 1.9.18p8. I have smbfs and the win95 bug workaround compiled into the kernel. Is there a solution to this? Also, I am

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

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

Seems that autofs in 6.2 stopped working like it used to. We use NIS and automount maps. Primary map auto.sf ssdt -fstype=autofs,rw auto_ssdt auto.ssdt map scratch -fstype=nfs,hard,intr gold:/vol/ssdt/scratch So finding a path such as /sf/ssdt/scratch has always worked and continues to work on non CentOS 6.2 machines. This ability stopped with CentOS 6.2 CentOS 6.0 uses

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

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

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

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 |

I've run into a problem that I've found no existing solution to. Any help with this problem would be greatly appreciated. I've outlined the requirements below. *** Linux users need to access Windows shares without typing out the entire mount command. For example, with automounter /net functionality a user can simply cd /net/HOSTNAME/EXPORT and gain access to the nfs export if he

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

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

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

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 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 *any* process attempts to access /mnt/syno-fredex or /mnt/syno-public, you'll get those

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.

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>

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