up2date

samba/files/smb.conf.jinja

@@ -0,0 +1,34 @@
+#
+# Managed by Salt
+#
+# run testparm -s after making changes to validate them
+
+[global]
+  workgroup = WORKGROUP
+  log file = /var/log/samba/log.%m
+  max log size = 1000
+  logging = file
+  panic action = /usr/share/samba/panic-action %d
+  server role = standalone server
+  obey pam restrictions = yes
+  unix password sync = no
+  map to guest = bad user
+  usershare max shares = 0
+
+{% if salt.pillar.get('samba:enable_homes', false) %}
+[homes]
+  comment = Home Directories
+  browseable = no
+  read only = yes
+  create mask = 0700
+  directory mask = 0700
+  valid users = %S
+{% endif %}
+
+{% for name, path in salt.pillar.get('samba:shares', {}).items() %}
+[{{ name }}]
+  path = {{ path }}
+  valid users = @sambashare
+  read only = yes
+{% endfor %}
+

samba/files/wsdd.service

@@ -0,0 +1,22 @@
+[Unit]
+Description=Web Services Dynamic Discovery host daemon
+; Start after the network has been configured
+After=network-online.target
+Wants=network-online.target
+; It makes sense to have Samba running when wsdd starts, but is not required
+;Wants=smb.service
+
+[Service]
+Type=simple
+ExecStart=/usr/bin/wsdd --shortlog
+; Replace those with an unprivledged user/group that matches your environment,
+; like nobody/nogroup or daemon:daemon or a dedicated user for wsdd
+User=nobody
+; The following lines can be used for a chroot execution of wsdd.
+; Also append '--chroot /run/wsdd/chroot' to ExecStart to enable chrooting
+;AmbientCapabilities=CAP_SYS_CHROOT
+;ExecStartPre=/usr/bin/install -d -o nobody -g nobody -m 0700 /run/wsdd/chroot
+;ExecStopPost=rmdir /run/wsdd/chroot
+
+[Install]
+WantedBy=multi-user.target