Hi, Gian Piero Carrubba wrote: > Init: sysvinit (via /sbin/init)
Diederik de Haas wrote: > And indeed 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). > (And is a Xen dom0 host.) This is indeed unrelated. For me it was a Xen DomU (i.e. a Xen guest host) and an EeePC 900A (i.e. a netbook) without any virtualisation. Diederik de Haas wrote: > On vrijdag 18 maart 2022 23:28:33 CET Diederik de Haas wrote: > > And indeed I do not have a /run/samba/ directory on my Bookworm > > system/server. > > After I manually created /run/samba/, the installation succeeded. So I suspect that the init script for some reason no more creates that directory. Diederik de Haas wrote: > Two years later and this issue still exists? I saw Axel already updated > the 'found' version so I won't have to do this. 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. Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE