[Bug 198064] net/samba41: 4.1.17 seems to change necessary rc.conf option for winbindd
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu Feb 26 23:08:53 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=198064
Bug ID: 198064
Summary: net/samba41: 4.1.17 seems to change necessary rc.conf
option for winbindd
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: timur at FreeBSD.org
Reporter: xenomorph at gmail.com
Assignee: timur at FreeBSD.org
Flags: maintainer-feedback?(timur at FreeBSD.org)
I just updated from samba41-4.1.16 to samba41-4.1.17 and immediately noticed
that winbindd no longer loaded with the rest of the samba services.
One of the features with samba41 (compared to samba36, for example) is less
stuff needed in /etc/rc.conf (http://www.freshports.org/net/samba41). You just
need 'samba_server_enable="YES"' to enable the nmbd/smbd/winbindd services.
With 4.1.17, I now need to add 'winbindd_enable="YES"' again (just like I did
with net/samba36).
Some of the changes in the samba41-4.1.17 package were with how the
winbindd_enable option was used:
https://svnweb.freebsd.org/ports/head/net/samba41/files/samba_server.in?r1=379838&r2=379837&pathrev=379838
The original port says that the samba startup script "tries it's[sic] best to
guess which out of samba/nmbd/smbd/winbindd daemons have to be started"
Does the 4.1.17 startup script no longer determine I needed winbindd? Based off
of what? Was this change intentional? Could this be something that is just
impacting me somehow?
I did not see any mention of changes with samba41 or winbindd in
/usr/ports/UPDATING.
--- Comment #1 from Bugzilla Automation <bugzilla at FreeBSD.org> ---
Auto-assigned to maintainer timur at FreeBSD.org
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list