I’ve got a Samba server set up on my computer with the following smb.conf:
[global]
workgroup = SAMBA
security = user
map to guest = Bad User
passdb backend = tdbsam
printing = cups
printcap name = cups
interfaces = lo virbr0
bind interfaces only = true
guest account = nobody
[printers]
path = /var/spool/samba
printable = yes
browseable = no
[LinuxHost]
comment = Host SAMBA Server for VM
path = /home/bob323/libvirt-shared
guest ok = yes
force user = nobody
force group = nobody
directory mask = 777
writable = yes
read only = no
create mode = 0777
directory mode = 0777
My setup is detailed in another thread:
but I’ll provide any additional details here if necessary.
Recently, I’ve been having an issue with my virtual machine not connecting until I restart the smb service. Is there anything I can check to troubleshoot what’s causing this? As soon as I run sudo systemctl restart smb
the VM connects without a problem, but if I check the status of the service before this it says it’s active and was loaded successfully. There are a few messages underneath the regular systemd status output:
Nov 28 11:15:49 localhost.localdomain systemd[1]: Starting Samba SMB Daemon...
Nov 28 11:15:49 localhost.localdomain smbd[2575]: [2019/11/28 11:15:49.821046, 0] ../../lib/util/become_daemon.c:135(daemon_ready)
Nov 28 11:15:49 localhost.localdomain smbd[2575]: daemon_ready: daemon 'smbd' finished starting up and ready to serve connections
Nov 28 11:15:49 localhost.localdomain systemd[1]: Started Samba SMB Daemon.
Any recommendations?