Closed issue by hk0O7 on void-packages repository

https://github.com/void-linux/void-packages/issues/32079

Description:
### System

* xuname: Void 5.4.83_1 armv6l Unknown uptodate rFF
* package: samba-4.14.5_1

### Expected behavior
Being able to start `smbd` with the default configuration.

### Actual behavior
It immediately ends with:
```
exit_daemon: daemon failed to start: Samba cannot setup ep pipe, error code 13
```

### Steps to reproduce the behavior
```
# xbps-install -Suy samba
# smbd -FS -d 10 --no-process-group
    ...
    regdb_open: registry db opened. refcount reset (1)
    make_internal_ncacn_conn: Create pipe requested winreg
    Created internal pipe winreg
    svcctl_init_winreg: Could not open SYSTEM\CurrentControlSet\Services - NT_STATUS_INVALID_HANDLE
    regdb_close: decrementing refcount (1->0)
    dcesrv_init_ep_server: Failed to init endpoint server 'svcctl': NT_STATUS_UNSUCCESSFUL
    dcesrv_init: Failed to init DCE/RPC endpoint servers: NT_STATUS_UNSUCCESSFUL
    main: Failed to setup RPC server: NT_STATUS_UNSUCCESSFUL
    exit_daemon: daemon failed to start: Samba cannot setup ep pipe, error code 13
```
After this, two (forked?) `smbd` processes for the given command will remain, and thus trying to start it from runit with `sv start smbd` will end up filling up the system with `smbd -F -S -d1` processes.

This looks like the same issue that was mentioned by [wangp][1] and [Anachron][2] in #27565 for samba-4.13.2_2.

[1]: https://github.com/void-linux/void-packages/issues/27565#issuecomment-753282396 
[2]: https://github.com/void-linux/void-packages/issues/27565#issuecomment-753361331