Well, I do not want to do that for a single reason:
SSSD is unfortunately still buggy enough to go offline (at least chances are high) when
machine is restarted.
With tmpfs, my automouter would be busted that way and several serviced would not start
Luckily enough, there is still an option to mount it via NFSv3. That way, even if sssd
goes offline, it still has sufficient data in cache for automounter to start properly.
[mailto:firstname.lastname@example.org] On Behalf Of Lukas Slebodnik
Sent: 18 September 2015 09:54
To: End-user discussions about the System Security Services Daemon
Subject: Re: [SSSD-users] Race condition when /var/lib/sssd in on NFSv4
On (16/09/15 09:29), Jakub Hrozek wrote:
On Wed, Sep 16, 2015 at 07:21:17AM +0000, Ondrej Valousek wrote:
> Hi list,
> I have just discovered that there is a race condition when we put /var/lib/sssd on
NFSv4 volume (such as in diskless boot scenario).
> System tends to hang randomly.
> Is there any solution to this?
> Only cure seems to me at the moment to mount it via NFSv3 which does not require
Simo or other more seasoned Samba developers might know better, but
IIRC tdb (the underlying key-value store our ldb cache uses) wasn't
usable well on NFS due to some locking issues..
So the solution/workaround is to mount tmpfs on /var/lib/sss/db/ on diskless
sssd-users mailing list
The information contained in this e-mail and in any attachments is confidential and is
designated solely for the attention of the intended recipient(s). If you are not an
intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or
any part thereof. If you have received this e-mail in error, please notify the sender by
return e-mail and delete all copies of this e-mail from your computer system(s). Please
direct any additional queries to: communications(a)s3group.com. Thank You. Silicon and
Software Systems Limited (S3 Group). Registered in Ireland no. 378073. Registered Office:
South County Business Park, Leopardstown, Dublin 18.