[Pkg-samba-maint] Bug#953530: samba-common-bin: post-install fails with "lock directory /run/samba does not exist"

Diederik de Haas didi.debian at cknow.org
Wed Mar 23 13:38:30 GMT 2022


On woensdag 23 maart 2022 06:54:57 CET Axel Beckert wrote:
> Gian Piero Carrubba wrote:
> > Init: sysvinit (via /sbin/init)
> 
> Diederik de Haas wrote:
> > I do not have a /run/samba/ directory on my Bookworm system/server.
> > I don't think it's relevant, but it (still?) has sysv-init as init.
> I think, I see a pattern here: My three affected hosts have sysvinit,
> too (on purpose).

Yeah, that's a pattern :-)

Looking a bit further and I found https://bugs.debian.org/975422 through
https://salsa.debian.org/samba-team/samba/-/commit/0c3b2056764cd1a566766c3e1764d7c312eab5d7
titled: "Ensure systemd-tmpfiles is called before testparm (Closes: #975422)"

This seems highly relevant for this issue.

On woensdag 23 maart 2022 06:54:57 CET Axel Beckert wrote:
> The reason why this pops up now with multiple people again is probably
> that we had a bunch of important kernel updates and hence reboots and
> empty /run/ tmpfs after reboot — which brings up this issue again even
> if you had created /run/samba/ manually after the previous reboot.

My (Xen Dom0) *Bookworm* system/server is somewhat unusual in that it's off
most of the time and reboots (or cold boots) happen more regular then what
most people expect for a Xen Dom0 system.
Not sure what to make of this and whether it's relevant ...

Cheers,
  Diederik
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-samba-maint/attachments/20220323/08598147/attachment.sig>


More information about the Pkg-samba-maint mailing list