search for: samba_restart_on_update

...; to use the classic smbd/nmbd/winbind daemons # "ad" to use the Active Directory server (which starts the smbd on its own) # (Be aware that you also need to enable the services/init scripts that # automatically start up the desired daemons.) SAMBA_START_MODE="classic" # SAMBA_RESTART_ON_UPDATE defines if the the services should be restarted when # the RPMs are updated. Setting this to "yes" effectively enables the # functionality of the try-restart parameter of the init scripts. SAMBA_RESTART_ON_UPDATE="yes" # NMBD_EXTRA_OPTS may contain extra options that are passed...

Hi, We are running sernet samba, and on one particular DC (debian 7.11, samba 4.5.6), when logrotate is ready rotating, "sernet-samba-ad restart" fails with: > Shutting down SAMBA AD services : ...trying once more ... (warning). > ...trying once more ... (warning). ..... > ...trying once more ... (warning). > Error: /usr/sbin/samba still running with PID=14755 from

...a-ad.service Prüfen ob kein Samba mehr läuft: pgrep samba und anschließend wieder starten: systemctl start sernet-samba-ad.service Eventuell auch die Konfiguration prüfen, sodass Samba automatisch neugestartet wird, wenn ein Update durchgeführt wird: # grep RESTART /etc/default/sernet-samba # SAMBA_RESTART_ON_UPDATE defines if the the services should be restarted when SAMBA_RESTART_ON_UPDATE="yes" Viele Grüße, Björn -- SerNet GmbH, Bahnhofsallee 1b, 37081 Göttingen phone: +49-551-370000-0, fax: +49-551-370000-9 AG Göttingen, HRB 2816, GF: Dr. Johannes Loxen http://www.sernet.de, mailto:kontakt at...

...and within it read that users need to edit "/etc/default/sernet-samba" as follows: # ---- SETUP SAMBA: service ad / smb / nmbd # enabled ad in /etc/default/sernet-samba for the AD server. vi /etc/default/sernet-samba # change this to : SAMBA_START_MODE="ad" # change : SAMBA_RESTART_ON_UPDATE="yes" Then I restarted the server and 'service --status-all' shows sernet-samba-ad service with a plus sign (+) which meant it was running. Then all the usual samba, krb5 and host "tests" returned correct results. I then went to one of my W7 clients, changed the dn...

...dit "/etc/default/sernet-samba" as follows: > ># ---- SETUP SAMBA: service ad / smb / nmbd > ># enabled ad in /etc/default/sernet-samba for the AD server. > >vi /etc/default/sernet-samba > ># change this to : SAMBA_START_MODE="ad" > ># change : SAMBA_RESTART_ON_UPDATE="yes" > >Then I restarted the server and 'service --status-all' shows >sernet-samba-ad service with a plus sign (+) which meant it >was running. > > >Then all the usual samba, krb5 and host "tests" returned correct >results. > >I then wen...

Hi, i upgrade to sles sp1 with sernet packages and get the following error after upgrade. Its looks like that port 135 will not reached. Anyone who have an information about that or a solution? Thanks Sven orion:~ # samba-tool drs showrepl Failed to connect host 192.168.24.2 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 192.168.24.2 (orion.domain.local) on port 135 -

...t administrator type: klist # # ------------------------------------------------------- # # ---- SETUP SAMBA: service ad / smb /nmbd # enabled ad in /etc/default/sernet-samba for the AD server. mcedit /etc/default/sernet-samba # change this to : SAMBA_START_MODE="ad" # change ???? : SAMBA_RESTART_ON_UPDATE="yes" # # Do not start samba yet. # # # Join the domain. samba-tool domain join SUBDOMAIN.DOMAIN.TLD DC -Uadministrator --realm=SUBDOMAIN.DOMAIN.TLD --dns-backend=BIND9_DLZ # and at the end you see: # Joined domain ROTTERDAM (SID S-1-5-21-3130855540-2228390408-1497266713) as a DC #...