In persistent mounts (found in /etc/fstab), there's two settings that tell the init process in which phase to run fsck and in which phase to mount. So in persistent mounts, it's easy to order the mounts during boot time. If necessary. And (as you say, the "_netdev" flag tells the boot process to mount a fs very late.)
I'm not sure that sorting the lines in /etc/fstab would accomplish this, I thought modern Linux versions fsck in parallel now, not sequentially. (I know they probe multiple SCSI buses in parallel.) But I suppose autofs has no concept of mount phase? Spike On Wed, Dec 4, 2019 at 4:36 AM Pavel Březina <pbrez...@redhat.com> wrote: > On 11/30/19 5:41 PM, Oguzhan Eris wrote: > > Hi everyone. > > > > First off, thanks to everyone who's ever worked on SSSD. It's easily in > my top 5 favorite FOSS projects out there. > > > > I am not sure if this is the right way to ask for an enhancement, or > whether I should file an issue on GitHub, but I am running into an issue > that's described in this Red Hat page > https://access.redhat.com/solutions/3673501 (login required) > > > > Basically for an automount map where I need nested top level paths: > > > > /mnt/foo > > /mnt/foo/bar > > > > each defined by their own map objects. SSSD does not handle this > (neither does LDAP directly from autofs) because the return map from LDAP > is unsorted, and if the maps are provided to autofs ordered as: > > > > /mnt/foo/bar > > /mnt/foo > > > > the /mnt/foo map masks the previous /mnt/foo/bar map and you'll only > get the entries from /mnt/foo > > > > Using file based mount maps, one can easily sort the top level maps, and > get around this issue. > > Would it be possible to have SSSD return the maps from LDAP query in a > sorted way? There is an LDAP control that most LDAP servers support to > return a sorted output, ( > > https://ldapwiki.com/wiki/Server%20Side%20Sort%20Control ) but with so > many clients and a large list, this might be better left to the client to > do instead. > > > > I'm happy to help out if someone can point me in the right direction in > the code. > > SSSD is just a data provider, if some sorting is needed I do not think > it should be done in SSSD (unless autofs interface says so) but rather > in autofs itself. > > CCing Ian, do you have any thoughts on this? > > > > > Thanks again > > _______________________________________________ > > sssd-users mailing list -- sssd-users@lists.fedorahosted.org > > To unsubscribe send an email to sssd-users-le...@lists.fedorahosted.org > > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > List Archives: > https://lists.fedorahosted.org/archives/list/sssd-users@lists.fedorahosted.org > > > _______________________________________________ > sssd-users mailing list -- sssd-users@lists.fedorahosted.org > To unsubscribe send an email to sssd-users-le...@lists.fedorahosted.org > Fedora Code of Conduct: > https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedorahosted.org/archives/list/sssd-users@lists.fedorahosted.org >
_______________________________________________ sssd-users mailing list -- sssd-users@lists.fedorahosted.org To unsubscribe send an email to sssd-users-le...@lists.fedorahosted.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedorahosted.org/archives/list/sssd-users@lists.fedorahosted.org
