"All SSSD client libraries (nss, pam, etc) won't serialize requests anymore by default, i.e. requests from multiple threads can be executed in parallel. Old behavior (serialization) can be enabled by setting environment variable "SSS_LOCKFREE" to "NO"."
Debian unstable is carrying this upstream version, but with a major modification on how the package handles the /etc/nsswitch.conf file. There is a new dh sequencer called "dh-nss" which aims at making the /etc/nsswitch.conf update process smoother, but there are a few rough edges that are being sorted out and, for that reason, I don't consider it stable enough to be shipped in Ubuntu yet. I intend to revert the dh-nss change for now and carry it as a delta. I have been working with the dh-nss maintainer in order to be able to have a stable sssd for next cycle.
The new sssd package builds fine on Kinetic, as can be seen here:
sssd 2.7.3 was released back in July and brings an important improvement to users, as can be seen in its changelog:
https:/ /github. com/SSSD/ sssd/releases/ tag/2.7. 3
"All SSSD client libraries (nss, pam, etc) won't serialize requests anymore by default, i.e. requests from multiple threads can be executed in parallel. Old behavior (serialization) can be enabled by setting environment variable "SSS_LOCKFREE" to "NO"."
Debian unstable is carrying this upstream version, but with a major modification on how the package handles the /etc/nsswitch.conf file. There is a new dh sequencer called "dh-nss" which aims at making the /etc/nsswitch.conf update process smoother, but there are a few rough edges that are being sorted out and, for that reason, I don't consider it stable enough to be shipped in Ubuntu yet. I intend to revert the dh-nss change for now and carry it as a delta. I have been working with the dh-nss maintainer in order to be able to have a stable sssd for next cycle.
The new sssd package builds fine on Kinetic, as can be seen here:
https:/ /launchpad. net/~sergiodj/ +archive/ ubuntu/ sssd-merge/ +packages
Its reverse Build-Depends are:
* autofs (for sssd-common) libsss- nss-idmap) libipa- hbac) nss-idmap- dev)
* freeipa (for python3-
* freeipa (for python3-sss)
* freeipa (for python3-
* slapi-nis (for libsss-
They also build fine against the new sssd:
https:/ /launchpad. net/~sergiodj/ +archive/ ubuntu/ sssd-merge- kinetic/ +packages
The autopkgtest results for the new sssd are also passing:
Results: (from http:// autopkgtest. ubuntu. com/results/ autopkgtest- kinetic- sergiodj- sssd-merge/ ?format= plain) autopkgtest. ubuntu. com/results/ autopkgtest- kinetic- sergiodj- sssd-merge/ kinetic/ amd64/s/ sssd/20220903_ 042948_ 718f7@/ log.gz 7.3-2ubuntu1~ ppa2 autopkgtest. ubuntu. com/results/ autopkgtest- kinetic- sergiodj- sssd-merge/ kinetic/ arm64/s/ sssd/20220903_ 043150_ f85a9@/ log.gz 7.3-2ubuntu1~ ppa2 autopkgtest. ubuntu. com/results/ autopkgtest- kinetic- sergiodj- sssd-merge/ kinetic/ armhf/s/ sssd/20220903_ 044318_ 5af0f@/ log.gz 7.3-2ubuntu1~ ppa2 autopkgtest. ubuntu. com/results/ autopkgtest- kinetic- sergiodj- sssd-merge/ kinetic/ ppc64el/ s/sssd/ 20220903_ 042902_ f85a9@/ log.gz 7.3-2ubuntu1~ ppa2 autopkgtest. ubuntu. com/results/ autopkgtest- kinetic- sergiodj- sssd-merge/ kinetic/ s390x/s/ sssd/20220903_ 042643_ 68c49@/ log.gz 7.3-2ubuntu1~ ppa2
sssd @ amd64:
http://
03.09.22 04:29:48 ✅ Triggers: sssd/2.
sssd @ arm64:
http://
03.09.22 04:31:50 ✅ Triggers: sssd/2.
sssd @ armhf:
http://
03.09.22 04:43:18 ✅ Triggers: sssd/2.
sssd @ ppc64el:
http://
03.09.22 04:29:02 ✅ Triggers: sssd/2.
sssd @ s390x:
http://
03.09.22 04:26:43 ✅ Triggers: sssd/2.