lingpanda101 at gmail.com
2016-Mar-23 14:36 UTC
[Samba] Starting & Stopping Samba (smb.conf modifications)
Hello, If I make a change to the smb.conf file. Can I simply invoke 'smbcontrol all reload-config', or must I kill all samba services and restart them? -- -James
Reindl Harald
2016-Mar-23 17:47 UTC
[Samba] Starting & Stopping Samba (smb.conf modifications)
Am 23.03.2016 um 15:36 schrieb lingpanda101 at gmail.com: If I make a change to the smb.conf file. Can I simply invoke> 'smbcontrol all reload-config', or must I kill all samba services and > restart them?[root at rh:~]$ cat /etc/systemd/system/smb.service [Unit] Description=Samba SMB Daemon [Service] Type=forking LimitNOFILE=32768 ExecStart=/usr/sbin/smbd -D ExecReload=/usr/bin/kill -HUP $MAINPID -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20160323/bdd94ddb/signature.sig>
Miguel Medalha
2016-Mar-23 22:46 UTC
[Samba] Starting & Stopping Samba (smb.conf modifications)
> If I make a change to the smb.conf file. Can I simply invoke > 'smbcontrol all reload-config', or must I kill all samba services and > restart themFor most changes you can do 'smbcontrol all reload-config'. From my experience, changes in shares often require a restart of the services.
Reindl Harald
2016-Mar-23 23:49 UTC
[Samba] Starting & Stopping Samba (smb.conf modifications)
Am 23.03.2016 um 23:46 schrieb Miguel Medalha:>> If I make a change to the smb.conf file. Can I simply invoke >> 'smbcontrol all reload-config', or must I kill all samba services and >> restart them > > For most changes you can do 'smbcontrol all reload-config'. From my > experience, changes in shares often require a restart of the servicesbesides that SIGHUP reloads configs when i comment out a share it disappears without a hard restart- the only problem are as so often apple clients which are closing the connecting due a reload (a few days ago cleaned up samab configs, SIGHUP and the phone ringed because two users got a disconnect message) [root at srv-rhsoft:~]$ > samba.log [root at srv-rhsoft:~]$ killall -s SIGHUP smbd [root at srv-rhsoft:~]$ cat samba.log [2016/03/24 00:44:58.223044, 1] ../source3/printing/queue_process.c:247(bq_sig_hup_handler) Reloading pcap cache after SIGHUP [2016/03/24 00:44:58.223042, 1] ../source3/smbd/server.c:1065(smbd_parent_sig_hup_handler) parent: Reloading services after SIGHUP [2016/03/24 00:44:58.321986, 1] ../source3/printing/queue_process.c:247(bq_sig_hup_handler) Reloading pcap cache after SIGHUP P.S.: i *hate* this cluttering with source-files and lines -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20160324/a1d55c60/signature.sig>