search for: menzing

hello, I have the following problem setting parameter 'frac' in the sigest function of the kernlab package. ## executing the ?sigest example: library(kernlab) data(spam) srange <- sigest(type~.,data = spam) ## works fine... ## setting 'frac' explicitly ## (in this case even to the default of .25) options(error=recover) srange <- sigest(type~.,data = spam, frac = .25) ##

When compiling samba-3.0.7 on Redhat-7.2, stock kernel 2.4.26, I get undefined references: ------- Compiling libads/ads_status.c with -fPIC Linking nsswitch/libnss_wins.so lib/system.po: In function `sys_dlopen': lib/system.po(.text+0xc17): undefined reference to `dlopen' lib/system.po: In function `sys_dlsym': lib/system.po(.text+0xc3b): undefined reference to `dlsym'

Hi all, I downloaded Samba 3.0.7 (gzipped) from samba.org to RedHat Linux, unzipper, and configured source. I got the following error during compilation Linking nsswitch/libnss_wins.so lib/system.po: In function `sys_dlopen': lib/system.po(.text+0xb37): undefined reference to `dlopen' lib/system.po: In function `sys_dlsym': lib/system.po(.text+0xb57): undefined reference to

Hi Folks, I compared the makefile for samba 3.0.6 and 3.0.7. I found XML_LIBS= MYSQL_LIBS= PGSQL_LIBS= these 3 lines and then the use of these variables missing in the 3.0.7 makefile. Thats the only change I found in 3.0.6 makefile and 3.0.7 makefile. So when I compiled samba 3.0.7 using the samba 3.0.6 makefile. It got compiled properly without any warnings of dlopen. I am not sure if

Dear all, A while ago I posted a message regading the way Samba is behaving and some problems that I was facing with Windows "loosing" the connection with the server... Here is another sample of what my /var/log/messages still looks like: Sep 19 15:08:01 Srv smbd-classic[3499]: [2004/09/19 15:08:01, 0] lib/util_sock.c:read_data(436) Sep 19 15:08:01 Srv smbd-classic[3499]:

Heinz, I had exactly the same problem, and used ldbedit to apply the fix. Thanks for digging into this! Now I'm interested in the root cause as well ... Uli Am 16.01.2018 um 16:48 schrieb Heinz Hölzl via samba: > no, it seems to work!!! > > > i did a ldapmodify on DC2: > > ldapmodify -x -h dc2 -D cn=administrator,cn=users,dc=test,dc=net -W -f > serverReference.ldif

Hi, there is no firewall, all DCs are in the same subnet. here ist the output of a test, you can see, the CNAME guid entries in the _msdcs can be resolved on any DC: (DC1 and DC2 are the first and second DCs, SAMBA3 was added at last. ldbsearch -H /srv/samba/private/sam.ldb '(invocationId=*)' --cross-ncs objectguid # record 1 dn: CN=NTDS Settings,CN=DC2,CN=Servers,CN=Default-First-Site-

Wildlife Statistician/Spatial Modeler ? Silver Spring, MD Seeking a Wildlife Statistician/Spatial Modeler with demonstrated experience fitting advanced statistical spatial/spatiotemporal models to wildlife survey data. The statistician/modeler will conceive and execute spatial analyses and generate predictive maps of coastal and marine species distributions to support coastal planning. The

There is additional info in the logs of the source DC (dcdo1, log level 2, manually triggered another replication): ==================== [2017/12/27 12:31:29.695121,  2] ../source4/rpc_server/drsuapi/getncchanges.c:1731(getncchanges_collect_objects)   ../source4/rpc_server/drsuapi/getncchanges.c:1731: getncchanges on DC=ad,DC=kdu,DC=com using filter (uSNChanged>=5415) [2017/12/27

Rowland, - the DN "CN=DCNH1,..." exists on all 3 DCs (pointing the Sites and Services console to each of them). - I also checked that "samba-tool dbcheck" completes w/o showing errors. - the objectGUID DNS aliases of all DCs are resolvable against all 3 DCs' builtin DNS - I forced a full sync from the FSMO holder (dcge1) to the 2 other DCs which finished w/o errors. -

We have 3 ADCs based on Samba-4.7.4 (compiled from source,internal DNS)/ CentOS7: dcdo1,dcnh1 and dcge1. dcge1 holds all FSMO roles. The 3 ADCs are on different locations connected via IPSec based VPN. No traffic is filtered out. All 3 ADCs replicate fine except dcdo1 -->dcnh1. Symptom: [root at dcdo1 ~]# samba-tool drs replicate dcnh1.ad.kdu.com dcdo1.ad.kdu.com dc=ad,dc=kdu,dc=com