Actually that is why I asked the additional question... that this likely
could be something the package maintainer should fix.? :) Yeah, it maybe
that the package maintainer is just not aware that @PIDDIR@ should be used.
-DD
On 04/04/2021 10:42, Rowland penny via samba wrote:> On 04/04/2021 18:15, Dachshund Digital via samba wrote:
>> Is this an issue per se, is it going to be fixed at some point?
>>
>> [??? 6.590110] systemd[1]: /lib/systemd/system/smbd.service:9:
>> PIDFile= references path below legacy directory /var/run/, updating
>> /var/run/samba/smbd.pid ? /run/samba/smbd.pid; please update the unit
>> file accordingly.
>> [??? 6.662755] systemd[1]: /lib/systemd/system/nmbd.service:9:
>> PIDFile= references path below legacy directory /var/run/, updating
>> /var/run/samba/nmbd.pid ? /run/samba/nmbd.pid; please update the unit
>> file accordingly.
>>
>> This is something the package maintainer has to fix?? Since standard
>> samba does have sample unit files, it should at least be fixed in
>> those so the maintainer has a valid guide?
>>
>> This was found on debian 10 buster (ARMHF, not that the hardware
>> platform matters for this issue).
>>
>>
>
> How do you suggest Samba fixes 'PIDFile=@PIDDIR@/smbd.pid' ?
>
> This is down to the package maintainers to fix, they are setting
> '@PIDDIR@' to the wrong directory.
>
> Rowland
>
>
>
>
>