* Chris Hofstaedtler <[email protected]> [251228 13:27]:
On Sun, Dec 28, 2025 at 10:45:31AM +0100, Jochen Sprickerhof wrote:
* Chris Hofstaedtler <[email protected]> [2025-12-28 10:00]:
[..]
> Maybe `shadowconfig on` should just delete the lock file? Didn't
> investigate yet if this is feasible.
Probably also a good idea but that would be libc as shadowconfig is using
pwconv which is calling lckpwdf() and that is creating the lock file. Maybe
it should clean it up upon ulckpwdf().
Another option might be to ship /etc/.pwd.lock as a proper conffile
in a package. Even if src:shadow would clean up after installing,
other packages using lckpwdf will still cause this issue.
Given lckpwdf is in src:glibc, maybe there?
Chris
