samba - Jun 2017 - [4.2.14-Debian] Smbd not listening on 192.168.0.x on cold start

Am 19.06.2017 um 11:42 schrieb Winfried via samba:
> ### BEGIN INIT INFO
> # Provides:          samba
> # Required-Start:
> # Required-Stop:
> # Default-Start:
> # Default-Stop:
> # Short-Description: ensure Samba daemons are started (nmbd and smbd)
> ### END INIT INFO
well, there is no ordering with network services
most likely your samba starts before the network is fully up

with systemd you would just say "After=network.service 
systemd-networkd.service network-online.target" in the unit

Thanks. I'll see how to configure systemd so that Samba starts once the
network is up and running.



--
View this message in context:
http://samba.2283325.n4.nabble.com/4-2-14-Debian-Smbd-not-listening-on-192-168-0-x-on-cold-start-tp4720131p4720154.html
Sent from the Samba - General mailing list archive at Nabble.com.

On Mon, 19 Jun 2017 12:15:36 +0200
Reindl Harald via samba <samba at lists.samba.org> wrote:
> most likely your samba starts before the network is fully up
I thought systemd was supposed to make this impossible ?

Note: I am not trying to start a flamewar here, I am just asking a
question.
> 
> with systemd you would just say "After=network.service 
> systemd-networkd.service network-online.target" in the unit
> 
Problem is, the OP is using an init script

Rowland

So it looks like the init script in the Samba package in the Debian
repository needs to be edited for a non-DC home server.




--
View this message in context:
http://samba.2283325.n4.nabble.com/4-2-14-Debian-Smbd-not-listening-on-192-168-0-x-on-cold-start-tp4720131p4720160.html
Sent from the Samba - General mailing list archive at Nabble.com.

Am 19.06.2017 um 12:15 schrieb Winfried via samba:
> Thanks. I'll see how to configure systemd so that Samba starts once the
> network is up and running.
> 
> 
> 
> --
> View this message in context:
http://samba.2283325.n4.nabble.com/4-2-14-Debian-Smbd-not-listening-on-192-168-0-x-on-cold-start-tp4720131p4720154.html
> Sent from the Samba - General mailing list archive at Nabble.com.
> 
I don't know if it helps but I use the following systemd service configs
to start samba (AD or Members) with the interface names in the config,
never had a problem.

------------------- AD ---------------------

cat > /etc/systemd/system/samba-ad-dc.service << EOF
[Unit]
Description=Samba4 AD DC
After=network.target remote-fs.target nss-lookup.target

[Service]
Type=forking
ExecStart=/usr/sbin/samba -D
PIDFile=/var/run/samba/samba.pid

[Install]
WantedBy=multi-user.target
EOF

systemctl enable samba-ad-dc

------------------- Members ---------------------

cat > /etc/systemd/system/samba-smbd.service << EOF
[Unit]
Description=Samba4 smbd
After=network.target remote-fs.target nss-lookup.target

[Service]
Type=forking
ExecStart=/usr/sbin/smbd -D
PIDFile=/var/run/samba/smbd.pid

[Install]
WantedBy=multi-user.target
EOF"

systemctl enable samba-smbd

--

cat > /etc/systemd/system/samba-nmbd.service << EOF
[Unit]
Description=Samba4 nmbd
After=network.target remote-fs.target nss-lookup.target

[Service]
Type=forking
ExecStart=/usr/sbin/nmbd -D
PIDFile=/var/run/samba/nmbd.pid

[Install]
WantedBy=multi-user.target
EOF

systemctl enable samba-nmbd

--

cat > /etc/systemd/system/samba-winbindd.service << EOF
[Unit]
Description=Samba4 winbindd
After=network.target remote-fs.target nss-lookup.target

[Service]
Type=forking
ExecStart=/usr/sbin/winbindd -D
PIDFile=/var/run/samba/winbindd.pid

[Install]
WantedBy=multi-user.target
EOF

systemctl enable samba-winbindd



--
Bjoern