Learn more about these different git repos.
Other Git URLs
The auto.master map is only read on autofs daemon startup. It might make sense to always read it from LDAP if online to make sure the contents of the master map are up2date when autofs is restarted.
I discussed the enhancement with the autofs maintainer and here is the proposal:
The automounter only reads the master map on startup or when it receives SIGHUP (which is an explicit way of telling the automounter to re-read its configuration). That means it's quite a rare event, at the same time modifications to the master map are quite rare. In both cases the admin expects the changes to the map to propagate to the automounter deamon.
In SSSD, we should implement the same behaviour the automounter implements internally, which is:
1. when a request comes for the master map, completely bypass caching and go to the Data Provider
2. the master map is called auto.master in 99% of the cases. For the 1% where it's not, we might want to implement an option to override the map name (automounter has that option).
design_review: => 0
milestone: NEEDS_TRIAGE => SSSD 1.9.3
type: enhancement => defect
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=870045
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=870045 870045]
Not critical for 1.9.3
_comment0: Not critical for 1.9.4 => 1352200480568757
milestone: SSSD 1.9.3 => SSSD 1.9.4
Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=876531 (Red Hat Enterprise Linux 6)
rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=870045 870045] => [https://bugzilla.redhat.com/show_bug.cgi?id=870045 870045], [https://bugzilla.redhat.com/show_bug.cgi?id=876531 876531]
owner: somebody => jhrozek
patch: 0 => 1
status: new => assigned
resolution: => fixed
status: assigned => closed
Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.9.4
to comment on this ticket.