[Samba] Option configure

[Sonic]

On Tue, Jul 12, 2016 at 5:58 PM, Achim Gottinger <achim at ag-web.biz> wrote:
> With type=forking it shows (8591 is the pid in /var/run/samba/samba.pid)
>
> systemctl status samba-ad-dc
> ● samba-ad-dc.service - Samba AD Daemon

I get this:
=================================================================
# systemctl status samba.service
● samba.service - Samba AD server
  Loaded: loaded (/etc/systemd/system/samba.service; enabled)
  Active: active (running) since Tue 2016-07-12 14:39:17 EDT; 4h 44min ago
 Process: 21350 ExecStart=/usr/local/samba/sbin/samba (code=exited,
status=0/SUCCESS)
Main PID: 21351 (samba)
  CGroup: /system.slice/lxc.service/system.slice/samba.service
          ├─21351 /usr/local/samba/sbin/samba
          ├─21352 /usr/local/samba/sbin/samba
          ├─21354 /usr/local/samba/sbin/smbd -D --option=server role
check:inhibit=yes --foreground
          ├─21355 /usr/local/samba/sbin/samba
          ├─21356 /usr/local/samba/sbin/samba
          ├─21357 /usr/local/samba/sbin/samba
          ├─21358 /usr/local/samba/sbin/samba
          ├─21359 /usr/local/samba/sbin/samba
          ├─21360 /usr/local/samba/sbin/samba
          ├─21361 /usr/local/samba/sbin/samba
          ├─21362 /usr/local/samba/sbin/samba
          ├─21363 /usr/local/samba/sbin/winbindd -D --option=server
role check:inhibit=yes --foreground
          ├─21364 /usr/local/samba/sbin/samba
          ├─21365 /usr/local/samba/sbin/samba
          ├─21368 /usr/local/samba/sbin/winbindd -D --option=server
role check:inhibit=yes --foreground
          ├─21369 /usr/local/samba/sbin/smbd -D --option=server role
check:inhibit=yes --foreground
          ├─21370 /usr/local/samba/sbin/smbd -D --option=server role
check:inhibit=yes --foreground
          └─21372 /usr/local/samba/sbin/smbd -D --option=server role
check:inhibit=yes --foreground

Jul 12 19:14:17 kwad winbindd[21368]: [2016/07/12 19:14:17.981972,  0]
../source3/winbindd/winbindd_cm.c:1849(wb_open_internal_pipe)
Jul 12 19:14:17 kwad winbindd[21368]: open_internal_pipe: Could not
connect to lsarpc pipe: NT_STATUS_UNSUCCESSFUL
Jul 12 19:14:17 kwad winbindd[21368]: [2016/07/12 19:14:17.982073,  0]
../source3/winbindd/winbindd_cm.c:1849(wb_open_internal_pipe)
Jul 12 19:14:17 kwad winbindd[21368]: open_internal_pipe: Could not
connect to lsarpc pipe: NT_STATUS_UNSUCCESSFUL
Jul 12 19:19:17 kwad winbindd[21368]: [2016/07/12 19:19:17.985495,  0]
../source3/winbindd/winbindd_cm.c:1849(wb_open_internal_pipe)
Jul 12 19:19:17 kwad winbindd[21368]: open_internal_pipe: Could not
connect to dssetup pipe: NT_STATUS_UNSUCCESSFUL
Jul 12 19:19:17 kwad winbindd[21368]: [2016/07/12 19:19:17.985653,  0]
../source3/winbindd/winbindd_cm.c:1849(wb_open_internal_pipe)
Jul 12 19:19:17 kwad winbindd[21368]: open_internal_pipe: Could not
connect to lsarpc pipe: NT_STATUS_UNSUCCESSFUL
Jul 12 19:19:17 kwad winbindd[21368]: [2016/07/12 19:19:17.985747,  0]
../source3/winbindd/winbindd_cm.c:1849(wb_open_internal_pipe)
Jul 12 19:19:17 kwad winbindd[21368]: open_internal_pipe: Could not
connect to lsarpc pipe: NT_STATUS_UNSUCCESSFUL
=================================================================

Trying to figure out the anomaly with winbindd starting, although it is running.

Chris