We use LDAP to store all of our map data which seems to be working very well (all FC6 so autofs v5.0.1 RC3). First off, we found out the hardway that when autofs is restarted (like as part of a cron job) and a local autofs filesystem is in use (direct map) ... kernel panic. The restarting was originally so we could push new maps and clients we get the maps nightly. After the kernel panic fiasco, I nticed the reload option (should be much safer since in our enviornment it would almost always only be adding new maps). Sounds good, but it does not work. Reload fails as it cannot start TLS, so it loads a null map and kills all unused daemons. I have no idea why it cannot start TLS since the service has no issues when starting and I can see it querying ldap for the auto.master and the mount ou. So this leads to a few questions:
1. Does autofs only use the /etc/openldap/ldap.conf file, or does the reload function use the /etc/ldap.conf file I think that is a hold over for legacy applications) 2. Is there a good way to debug what exactly is failing with the reload? (I have logging set to debug but that give little useful info. 3. What is the best way to have clients poll for updates to the autofs maps? Thanks in advance.
_______________________________________________ autofs mailing list [email protected] http://linux.kernel.org/mailman/listinfo/autofs
