search for: uidn

...I presume that `R CMD check MASS' fails for some similar reason. The final output in MASS-Ex.Rout is: > library(nlme) > fp2 <- deriv(~ 0.5 + 0.5/(1 + exp(-(x-L75)/2)), + "L75", function(x,L75) NULL) > OMEi.nls <- nlsList(Correct/Trials ~ fp2(Loud, L75) | UIDn, + data = OMEi, start=list(L75=45), control = list(maxiter=100)) Error in nls(formula = formula, data = data, start = start, control = control) : maximum number of iterations exceeded [above message repeated another 10 times] Error in qr(attr(rhs, "gradient")) : NA/NaN/Inf in forei...

googled and tried stuff: # net ads search '(|(uidNumber=*)(gidNumber=*))' sAMAccountName uidNumber gidNumber -P | grep uidN | sort -n ... shows me uidNumbers: uidNumber: 0 uidNumber: 1000 .. up to 1077 So my idmap range was completely wrong, I assume. I now have on the member server: # cat /etc/samba/smb.conf [global] security = ADS wor...

On Sun, 1 Jan 2017 15:40:53 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > googled and tried stuff: > > # net ads search '(|(uidNumber=*)(gidNumber=*))' sAMAccountName > uidNumber gidNumber -P | grep uidN | sort -n > > ... shows me uidNumbers: > > uidNumber: 0 You definitely shouldn't have a user with the ID of '0' (in my opinion) Is this Administrator ? > uidNumber: 1000 > > .. up...

Hi We have AD users created with either samba-tool user add steve2 or using the windows AD frontend from a windows box. Users are created with home directories under /home/CACTUS On a win 7 client all works fine. Users can authenticate against the CACTUS domain and files are created with the correct uid:gid We joined an Ubuntu client to the domain using likewise. /home from the server is

On Sun, 1 Jan 2017 13:45:11 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 2017-01-01 um 13:29 schrieb Rowland Penny via samba: > > > Try checking in AD, as you have classicupgraded, your users should > > have uidNumber attributes. Find the lowest and the highest, do the > > same for groups and if you change to the 'ad' backend and set the > > range based on your lowest and highest numbers (remembering you > > will probably want to add new users, so add something to the > > hig...

...out top=0/0, retr=0/0, del=0/0, size=0 After much searching for anything different between these records, some tcpdumps showed that the problem occured when LDAP returned the attributes in a different order than they are requested in. In this sample, you can see the request for uid,homeDirectory,uidNumber,gidNumber,mailQuota and the values are returned in the order gidNumber, uid, uidNumber, homeDirectory. There is no mailQuota set for this user. 16:54:06.145597 IP mail.xxxxx.com.62929 > closest-ldap.ldap: P 14:261(247) ack 15 win 33304 <nop,nop,timestamp 1521221146 267819447> 0...