After a few reboot, it seems I found the quick-'n-elegant fix for that issue:
root@lucid-golden:~ # cat /etc/init/autofs-ldap.conf
# Restart AutoFS-LDAP after everything has settled
start on (stopped networking and stopped rc RUNLEVEL=[2345])
exec /etc/init.d/autofs restart
Problem with depending on 'portmap' is that it may not be installed (since 'autofs5' only recommends 'nfs-common' and indirectly 'portmap') and may not be necessary (it seems one may use autofs-ldap to mount other-than-NFS network filesystem, e.g. CIFS).
Now comes the issue of a (ported) /etc/init/autofs.conf: should it necessarily depend on 'networking' (and thus make the /etc/init/autofs-ldap.conf unnecessary) or can we imagine that autofs may be used for non-network filesystems (and should thus not depend on 'networking'; /etc/init/autofs-ldap.conf should thus be kept separate, with the 'networking' dependency but without the 'rc' one) ?
After a few reboot, it seems I found the quick-'n-elegant fix for that issue:
root@lucid-golden:~ # cat /etc/init/ autofs- ldap.conf
# Restart AutoFS-LDAP after everything has settled
start on (stopped networking and stopped rc RUNLEVEL=[2345])
exec /etc/init.d/autofs restart
Problem with depending on 'portmap' is that it may not be installed (since 'autofs5' only recommends 'nfs-common' and indirectly 'portmap') and may not be necessary (it seems one may use autofs-ldap to mount other-than-NFS network filesystem, e.g. CIFS).
Now comes the issue of a (ported) /etc/init/ autofs. conf: should it necessarily depend on 'networking' (and thus make the /etc/init/ autofs- ldap.conf unnecessary) or can we imagine that autofs may be used for non-network filesystems (and should thus not depend on 'networking'; /etc/init/ autofs- ldap.conf should thus be kept separate, with the 'networking' dependency but without the 'rc' one) ?
Hope this helps. Cheers