Void Server como Domain Control
O objetivo nesse tutorial é subir um Controlador de Domínio Primário no Void Linux (glibc) compilando o Samba4 a partir do código fonte, configurando DNS interno, Kerberos, integração AD, ACLs, serviços e toda a pilha necessária para controlar os clientes da rede, com uma floresta de nível 2016.
Parte 4: Criando os serviços do samba-ad-dc no runit
Agora vamos criar os serviços e permissões do samba-ad-dc com logs, para o runit subir no boot do Sistema:
# mkdir -p /var/log/samba-ad-dc
#!/bin/sh
exec 2>&1
exec /opt/samba/sbin/samba -i -M single --debuglevel=3
EOF
#!/bin/sh
exec svlogd -tt /var/log/samba-ad-dc
EOF
Habilitar o serviço do samba-ad-dc para subir no boot:
# ln -s /etc/sv/samba-ad-dc /var/service/
Validar se está rodando:
# sv status samba-ad-dc
Você deverá ver algo como:
run: samba-ad-dc: (pid 28032) 4s; run: log: (pid 28031) 4s
Validar os logs online:
# tail -f /var/log/samba-ad-dc/current
A saída correta será algo assim:
2025-11-27_04:14:23.73604 Completed DNS update check OK
2025-11-27_04:14:25.35809 Registered VOIDDC01<00> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:25.35814 Registered VOIDDC01<03> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:25.35815 Registered VOIDDC01<20> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:25.35941 Registered EDUCATUX<1b> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:25.35942 Registered EDUCATUX<1c> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:25.35944 Registered EDUCATUX<00> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:36.71381 Calling samba_kcc script
2025-11-27_04:14:37.31554 samba_runcmd_io_handler: Child /opt/samba/sbin/samba_kcc exited 0
2025-11-27_04:14:37.31557 Completed samba_kcc OK
Criar a estrutura do serviço antes de tudo
# mkdir -p /etc/sv/samba-ad-dc/log# mkdir -p /var/log/samba-ad-dc
Criar o serviço do run
# cat > /etc/sv/samba-ad-dc/run << 'EOF'#!/bin/sh
exec 2>&1
exec /opt/samba/sbin/samba -i -M single --debuglevel=3
EOF
Setar a permissão do serviço do run
# chmod +x /etc/sv/samba-ad-dc/runCriar o arquivo do log
# cat > /etc/sv/samba-ad-dc/log/run << 'EOF'#!/bin/sh
exec svlogd -tt /var/log/samba-ad-dc
EOF
Setar a permissão do log/run
# chmod +x /etc/sv/samba-ad-dc/log/runHabilitar o serviço do samba-ad-dc para subir no boot:
# ln -s /etc/sv/samba-ad-dc /var/service/
Validar se está rodando:
# sv status samba-ad-dc
Você deverá ver algo como:
run: samba-ad-dc: (pid 28032) 4s; run: log: (pid 28031) 4s
Validar os logs online:
# tail -f /var/log/samba-ad-dc/current
A saída correta será algo assim:
2025-11-27_04:14:23.73604 Completed DNS update check OK
2025-11-27_04:14:25.35809 Registered VOIDDC01<00> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:25.35814 Registered VOIDDC01<03> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:25.35815 Registered VOIDDC01<20> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:25.35941 Registered EDUCATUX<1b> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:25.35942 Registered EDUCATUX<1c> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:25.35944 Registered EDUCATUX<00> with 192.168.70.250 on interface 192.168.70.255
2025-11-27_04:14:36.71381 Calling samba_kcc script
2025-11-27_04:14:37.31554 samba_runcmd_io_handler: Child /opt/samba/sbin/samba_kcc exited 0
2025-11-27_04:14:37.31557 Completed samba_kcc OK