Date: Fri, 3 Jan 2020 10:15:14 -0800 From: Lee Damon <nomad@castle.org> To: Brooks Davis <brooks@freebsd.org> Cc: freebsd-stable@freebsd.org Subject: Re: amd and LDAP - a sad story Message-ID: <f7261976-f67f-6d7b-05fa-a6479b10756f@castle.org> In-Reply-To: <20200103175452.GK91104@spindle.one-eyed-alien.net> References: <44772535-277d-c50d-f93f-57b3e4162ed7@castle.org> <20200103175452.GK91104@spindle.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 1/3/20 09:54 , Brooks Davis wrote: > Adding nss_ldap to the mix makes all programs threaded so a bunch of > code paths are different. Unfortunately, amd is complicated, out of > date, and unmaintained so I'm not sure who will be able to help. If > possible, I would suggest putting effort into migrating to automount > rather than debugging amd since amd will be removed prior to FreeBSD 13. I was afraid that was going to be the answer. I have ~18 years worth of layering in the AMD maps. Converting isn't going to be fun and I've been putting it off for years but I guess it's time. Of course, I'm pushing against a deadline for this host and that deadline is well before I'll be able to finish the conversion. I guess it's time for duct tape and some bailing wire. The confusing thing to me is that the exact same set up, with the exact same FBSD release, works just fine for my existing hosts. nomad
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f7261976-f67f-6d7b-05fa-a6479b10756f>