When trying to set-up autofs to work with sssd I've hit a problem where after reinstalling sys-auth/sssd with autofs USE flag and adding 'sss' to /etc/nsswitch.conf under the 'automount' entry automount was missing the lookup_sss.so file. It turned out that after reinstalling net-fs/autofs the missing file magically appeared. This leads me to believe that net-fs/autofs checks for presence of sssd's autofs plugin and enables sssd support if it finds it. This should be reflected in the ebuild. The net-fs/autofs ebuild should have a 'sssd' USE flag that will trigger a dependency on sys-auth/sssd[autofs] Reproducible: Always Steps to Reproduce: 1. emerge net-fs/autofs 2. USE=autofs emerge sys-auth/sssd 3. automount -f Actual Results: automount fails with the following error: open_lookup:93: cannot open lookup module sss (/usr/lib64/autofs/lookup_sss.so: cannot open shared object file: No such file or directory) Expected Results: automount should start normally
Created attachment 469308 [details, diff] Added sys-auth/sssd as RDEPEND I could not reproduce the problem, however I added sys-auth/sssd as RDEPEND, in case it by others.
(In reply to christos kotsis from comment #1) > Created attachment 469308 [details, diff] [details, diff] > Added sys-auth/sssd as RDEPEND > > I could not reproduce the problem, however I added sys-auth/sssd as RDEPEND, > in case it by others. in case it is needed by others**
Comment on attachment 469308 [details, diff] Added sys-auth/sssd as RDEPEND >--- auto-fs-runtime-dep 2017-04-06 03:17:22.693698131 +0300 >+++ auto-fs-runtime-dep-new 2017-04-06 03:25:28.168707905 +0300 >@@ -28,7 +28,9 @@ > REQUIRED_USE="sasl? ( ldap )" > > # currently, sasl code assumes the presence of kerberosV > RDEPEND=">=sys-apps/util-linux-2.20 >+ sys-auth/sssd > dmalloc? ( dev-libs/dmalloc[threads] ) > hesiod? ( net-dns/hesiod ) > ldap? ( >=net-nds/openldap-2.0
Created attachment 580228 [details, diff] patch for autofs-5.1.5-r1.ebuild This is still a problem as of today. The attached patch is a bit kludgy but should at least be a usable fix... The bigger problem here is that the configure script for autofs doesn't seem to have a flag to explicitly enable/disable sssd support (i.e. there is no --with-sssd/--without-sssd that we could control via USE=sssd). The configure script appears to rely *exclusively* on the presence/absence of /usr/{lib64,lib}/sssd/modules/libsss_autofs.so to set its internal HAVE_SSS_AUTOFS={1,0}. This patch deals with that by introducing an anti-dependency that should prevent libsss_autofs.so from existing when autofs is built with USE=-sssd. I don't like having to introduce a blocker case for this, but it's the least invasive method I can think of to ensure that USE=-sssd actually has the intended effect.
