similar to: Updated sources and clean build gives linker error in cldapd.o

Displaying 13 results from an estimated 13 matches similar to: "Updated sources and clean build gives linker error in cldapd.o"

2010 May 02
2
samba4 make error - drsblobs.so
Hello - make fails to build the latest git of samba4 - erroring on drsblobs.so. Below is a full log from autogen.sh to the make. Would you have any suggestions on proceeding? Thank you, Ryan ryan at test1:~/samba-master/source4$ sudo ./autogen.sh ./autogen.sh: running script/mkversion.sh ./script/mkversion.sh: 'version.h' created for Samba("4.0.0alpha12-GIT-d83850a")
2008 Jun 19
0
Error when complile samba 4 with python 2.5
Hi, When compile samba4 with python 2.5, I've got error below: n/mergedobj/python_svcctl.o: In function `py_SERVICE_LOCK_STATUS_get_lock_owner': py_svcctl.c:(.text+0x142): undefined reference to `PyUnicodeUCS2_Decode' bin/mergedobj/python_svcctl.o: In function `py_SERVICE_LOCK_STATUS_set_lock_owner': py_svcctl.c:(.text+0x227): undefined reference
2010 Jan 31
0
error compiling on 3.5 on OS X
I've tried to compile 3.5.0 RC2 on MAc OS X 10.6.2 and I get an error towards the end--- any help/ideas would be greatly appreciated--- -----------<snip>------------- torture/../../lib/util/tests/strlist.c:285: warning: passing argument 1 of ?str_list_equal? from incompatible pointer type torture/../../lib/util/tests/strlist.c: In function ?test_list_remove?:
2012 Apr 21
0
Cannot join domain with samba-3.6.4
Hello, We've been using samba for a while, up to version 3.4.x, without issues. We're having trouble joining an AD domain with 3.6.4 OS is Solaris 10 x64 Kerberos : MIT krb5 1.10.1 DC serveurs are running Windows 2008 The error message is : ./net ads join -U aranskis Enter aranskis's password: Failed to join domain: failed to lookup DC info for domain 'FOO.NET' over rpc:
2014 Feb 05
0
INTERNAL ERROR: Signal 11 in pid (kdc gone)
Hi There, We are getting INTERNAL ERROR: Signal 11 in pid on multiple different servers (Debian Wheezy, using Samba 4.0.13 and 4.1.3, using kernel 3.2.0-4 and 3.11.6-2), the outcome is always the same. The group policies can no longer be applied to the clients until a Samba4 restart. The locations with these issues do have in common that they have multiple Samba4 DC's although i am not
2010 Nov 11
1
FreeBSD 8.1 & Samba4 alpha11 domain controller - cldapd bind problem
I've been trying to run samba4 alpha11 on a FreeBSD 8.1 system as a domain controller but I'm having trouble starting the cldapd server. For some reason it won't bind to the specified address or interface whatever I specify in smb.conf. I managed running the provision script without any trouble but I have no clue how to solve this problem in order to start the samba server. bitrot#
2016 Oct 17
0
Bug 6870 resurfaced in Samba 4.2.10
On 2016-10-17 18:13, Jeremy Allison wrote: > On Mon, Oct 17, 2016 at 09:41:10AM -0700, Jeremy Allison via samba wrote: On Mon, Oct 17, 2016 at 05:13:08PM +0100, Rebecca Gellman via samba wrote: > > Hi, > > So I did some digging into the source code, and I think I've found the > issue. Around line 120 of source3/libads/cldap.c: > > for (i=0; i<num_servers;
2016 Oct 17
2
Bug 6870 resurfaced in Samba 4.2.10
On Mon, Oct 17, 2016 at 07:13:46PM +0100, Rebecca Gellman via samba wrote: > > > On 2016-10-17 18:13, Jeremy Allison wrote: > > > On Mon, Oct 17, 2016 at 09:41:10AM -0700, Jeremy Allison via samba wrote: On Mon, Oct 17, 2016 at 05:13:08PM +0100, Rebecca Gellman via samba wrote: > > > > Hi, > > > > So I did some digging into the source code, and I
2016 Oct 17
2
Bug 6870 resurfaced in Samba 4.2.10
On Mon, Oct 17, 2016 at 09:41:10AM -0700, Jeremy Allison via samba wrote: > On Mon, Oct 17, 2016 at 05:13:08PM +0100, Rebecca Gellman via samba wrote: > > > > > > Hi, > > > > So I did some digging into the source code, and I think I've found the > > issue. Around line 120 of source3/libads/cldap.c: > > > > for (i=0; i<num_servers;
2016 Oct 17
0
Bug 6870 resurfaced in Samba 4.2.10
On Mon, Oct 17, 2016 at 05:13:08PM +0100, Rebecca Gellman via samba wrote: > > > Hi, > > So I did some digging into the source code, and I think I've found the > issue. Around line 120 of source3/libads/cldap.c: > > for (i=0; i<num_servers; i++) { > NTSTATUS status; > > status = cldap_socket_init(state->cldap, > NULL, /* local_addr */
2019 Oct 23
0
winbind : suspend nightmare
On Mon, Oct 21, 2019 at 10:07:20AM +0200, Prunk Dump via samba wrote: > > I don't know if winbind "officially" support suspending. Currently I > have written a systemd hook that kill winbind before suspend and > restarting it after. It hasn't been tested in that mode as far as I know. Congratulations, you're the first ! :-). > 07:44:43 connection_ok:
2016 Oct 17
2
Bug 6870 resurfaced in Samba 4.2.10
Hi, So I did some digging into the source code, and I think I've found the issue. Around line 120 of source3/libads/cldap.c: for (i=0; i<num_servers; i++) { NTSTATUS status; status = cldap_socket_init(state->cldap, NULL, /* local_addr */ state->servers[i], &state->cldap[i]); if (tevent_req_nterror(req, status)) { return tevent_req_post(req, ev);
2019 Oct 21
5
winbind : suspend nightmare
Hello Samba Team ! First at all. It's seems that my problem is NOT (or not only) a Samba Winbind problem. But I need to understand what's happen to send good reports to correct maintainers. What's I'm trying to achieve : ------------------------------------------ Gnome gdm introduced a great feature that suspend the system on logout. This help a lot reducing the electric