Hi list, this is just a heads-up that SerNet does provide Samba 4 packages (including AD DC package) now. For more information, please see http://www.enterprisesamba.com/samba/ Cheers, Karolin -- 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 SerNet.DE
Hi there, [Sorry for cross-posting, I hope I didn't violated any list policies]> this is just a heads-up that SerNet does provide Samba 4 packages > (including AD DC package) now.It was told on the fedora user's list that the kerberos implementation used by Fedora, RHEL and CentOS conflicts with the samba one, and so Fedora was providing samba4 binaries without AD DC support. This was related to the use of FreeIPA by Fedora and RHEL. So I wasn't expecting to see packages with AD DC support for RHEL and CentOS so soon. Thanks a lot! But how did you manage the kerberos problem? I see you repo provides only samba4 packages, and do not replace any other library or daemin from CentOS and RHEL. Or would the problem be present only on newer Fedora releases, and not on RHEL6 (yet)? Would this be related to the fact servnet does not provide samba4 packages for Fedora, or you simply don't package anything for Fedora? Another question: if my CentOS server is using samba3 from sernet repos, may I upgrade them using sernet samba4? Or should I uninstall samba3 and do a clean install of samba4, redoing all configuration manually? []s, Fernando Lozano
There seems to be a problem with the "sernet-samba-ad" init script, at least on CentOS. Samba fails to start. The log file shows the following: [2013/05/15 20:48:37, 0] ../source4/smbd/server.c:369(binary_smbd_main) samba version 4.0.5-SerNet-RedHat-1.el6 started. Copyright Andrew Tridgell and the Samba Team 1992-2012 [2013/05/15 20:48:38, 0] ../source4/smbd/server.c:475(binary_smbd_main) samba: using 'standard' process model [2013/05/15 20:48:38, 0] ../file_server/file_server.c:47(file_server_smbd_done) file_server smbd daemon exited normally [2013/05/15 20:48:38, 0] ../source4/smbd/service_task.c:35(task_server_terminate) task_server_terminate: [smbd child process exited] [2013/05/15 20:48:38, 0] ../source4/smbd/server.c:210(samba_terminate) samba_terminate: smbd child process exited It looks like smbd starts and immediately exits. Under /var/run/samba, a process file samba.pid remains but not a smbd.pid file. Although samba is not running, the pidfile is left there. As a consequence, on further attempts to start samba using the script, it complains that a pidfile already exists. When samba is called by other means (/usr/sbin/samba or alternative init scripts) it starts and runs correctly. I am running 64bit CentOS 6.4. Thank you for your work.