I am using OpenSuSE 12.1 with homes shared through LDAP and NFS. ldap stores the maps. My problem is I can't have the shares mounted on boot. It's only working when restarting the autofs service manually. On a CentOS 6.3 there is no such problem.

My /etc/nsswitch.conf:

passwd: files sss
group:  files sss

hosts:  files mdns4_minimal [NOTFOUND=return] dns
networks:       files dns

services:       files
protocols:      files
rpc:            files
ethers:         files
netmasks:       files
netgroup:       files nis
publickey:      files

bootparams:     files
automount:      files ldap
aliases:        files

My /etc/openldap/ldap.conf:

SIZELIMIT       20
TIMELIMIT       15
#DEREF          never
TLS_REQCERT     demand
uri     ldap://
base    dc=domain,dc=com

My /etc/sssd/sssd.conf:

config_file_version = 2
reconnection_retries = 3
sbus_timeout = 30
services = nss, pam
domains = domain.com

filter_groups = root
filter_users = root
reconnection_retries = 3

reconnection_retries = 3

 id_provider = ldap
 auth_provider = ldap
 min_id = 500
 max_id = 30000
 ldap_schema = rfc2307
 ldap_uri =  ldaps://ldap-ms.local,  ldaps://ldap-sl.local, ldap://ldap
 ldap_search_base = dc=domain,dc=com
 ldap_user_search_base =  ou=People,dc=domain,dc=com
 ldap_group_search_base = ou=Group,dc=domain,dc=com
 ldap_tls_cacert = /etc/pki/CA/certs/domain-cacert.pem
 ldap_tls_reqcert = hard
 cache_credentials = true
 enumerate = True

My /etc/sysconfig/autofs:


Am I missing something?

  • 2
    Any chance your LDAP service is not available with the maps in time for the booting file system query? That would explain the later success with restart once the system is up and stable. – zedman9991 Jul 13 '12 at 17:57
  • What are the start-levels (within your target runlevel) for autofs and your ldap-client? – Nils Jul 13 '12 at 20:09
  • @zedman9991 This problem occurs only with my version of opensuse (12.1) On Centos 6.3 and OpenSuse 11.2 it works fine. – igor012 Jul 16 '12 at 9:02
  • @Nils Autofs starts on runlevels 3 and 5. – igor012 Jul 16 '12 at 9:02
  • There is a difference in the way autofs mounts maps on boot on opensuse 11.2 it mounts them at the access but on opensuse 12.1 it mounts them all but no access. – igor012 Jul 16 '12 at 10:04

Why not just add the mount locations to your fstab.

You could also use sshfs. Configure ssh to use public key authentication.

On the server:
sudo apt-get install openssh-server
Change to or add ServerKeyBits 2048 to /etc/ssh/sshd_config

On the Client
ssh-keygen -t rsa -b 2048
ssh-copy-id from the client computer to the server. Use your password for your user on the server machine to login
Change /etc/ssh/sshd_config: PasswordAuthentication no, UsePAM no
I use other settings as well to harden ssh but for this example it is not needed.
If your outside your lan setup a dyndns or noip updater, and setup portforwarding on your router so port 23 or what ever port you decide to use to obfuscate the service is forwarded to the server ip address, if you need help with that just ask.

I set this command as a launcher on the main menu for some drives and for others in the fstab.
I know it works because I use this same setup plus the hardening everyday.
This way you can get rid of the need for autofs and its required overhead.


This question got bumped by community, and it's pretty old.
A lot of things has happened over the years, Michael mentioned one solution, using fstab. And the original problem was most likely do due execution-order at boot time. Network might not have been ready, some service might not have started etc.

There's also another solution if you're running systemd (which I doubt OP did at the time, but if you end up here through a search, and you do) here's another solution using systemd's automount feature.

Description=Network mapping



The only drawback of this is that you have to be careful with what you name the service script. It's best described here, but a tl;dr-version is that the service-file must be named after the path it's going to mount. And all forward-slashes in said path has to be replaced with - in the service-file name for automatic mounting to work. The above example of /mnt/remote_share would be a service-file calledmnt-remote_share.mount`

There's a bunch of options to go with this.
If systemd isn't your thing, there's also a lot of new stuff on the autofs side which does a pretty good job (all be it a bit complicated for my taste).

If you want to use a fstab entry instead but utilize systemd's auto-hook feature, here's what your fstab could look like:   /mnt/remote_share  nfs  noauto,x-systemd.automount,x-systemd.device-timeout=10,timeo=14,x-systemd.idle-timeout=1min 0 0

And if neither of those work, there's also the pure-fstab solution:   /mnt/remote_share   nfs   defaults,soft,rsize=32768,wsize=32768,timeo=900,retrans=5,_netdev 0 0

I'll drop a few links to good documentation on the subject (bare in mind, it's a different OS. But their Wiki is as of writing this one of the best on the market):

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.