similar to: getGroups, nested mixed model

Hi all! I am working on a nested lme model with one fixed effect ("treatment", which 3 levels) and two random effects for "Individuals" (four of them) within "treatment" and "replicate -2 levels-" within "individual" within "treatment". For doing so, I´ve been trying to create a factor for Individual%in%Treatment, say IT by

Hi, I''m trying to understand the lme output and procedure. I''m using the Crawley''s book. I''m try to analyse the rats example take from Sokal and Rohlf (1995). I make a nested analysis using aov following the book. > summary(rats) Glycogen Treatment Rat Liver Min. :125.0 Min. :1 Min. :1.0 Min. :1 1st Qu.:135.8

Windows XP R 2.10 I am trying to run lme and get the following error: > fitRandom <- lme(values ~ subject, + data=withindata) Error in getGroups.data.frame(dataMix, groups) : Invalid formula for groups my data follows, below which is a copy of all my code > > print(withindata) subject values 1 1 2.3199639 2 1 -8.5795802 3 1 -4.1901241 4

Hi, I am running samba 3.0.7 on a FC 2 box with the following setup (testparm output): <snip> [global] workgroup = XXXXX realm = XXXXX.YYYYY.COM security = ADS log level = 1 log file = /var/log/samba/%m.log max log size = 50 load printers = No os level = 0 preferred master = No local master = No

On 03/10/2019 15:05, Satay Epic via samba wrote: > We have winbind client running on CentOS 7.3.1611 host connected to MS > active directory. It is working normal for local and AD users. However > in the logs, I see that NSS is throwing call to winbind to retrieve > the groups for "root" user. I wonder why it does and what can be done > to make it stop doing that. I

On 03/10/2019 15:46, Satay Epic wrote: > Thank you Rowland for your reply. My knowledge is limited with Samba > so please forgive me for any basic mistakes :) > This is something was setup by a previous admin. > > We have had issues where "winbind" will just "give up" and won't let > anyone login into the host not even from the console. > I would like

Ok. Wondering if it fix by changing the idmap backend to "ad" ? Is "ad" backend a better option than "rid" since we have MS AD or otherwise ? My next task is to ensure PAM is setup correctly with winbind. I'm going to validate the PAM configs. Do you have any recommendations of PAM / winbind settings? We also having "nscd" running for the DNS host

Dear all, I am looking at habituation of dogs trotting on a treadmill. Each record is made of 40 to 50 data for the same variable (for example Peak). I get each record at several minutes (1, 2 and 4) for each session. And I have 4 sessions of training (one session a week). The aim is to study the effect of the factor (Minute) on the Peak variable, and to study the changes of this effect

SSSD is not installed but I did remove it from nsswitch.conf. I still see winbind always doing the group lookup for local user. On Thu, Oct 3, 2019 at 8:05 AM Rowland penny via samba <samba at lists.samba.org> wrote: > > On 03/10/2019 15:46, Satay Epic wrote: > > Thank you Rowland for your reply. My knowledge is limited with Samba > > so please forgive me for any basic

Thank you Rowland for your reply. My knowledge is limited with Samba so please forgive me for any basic mistakes :) This is something was setup by a previous admin. We have had issues where "winbind" will just "give up" and won't let anyone login into the host not even from the console. I would like to fix that problem so started to investigate the configs. I don't

We have winbind client running on CentOS 7.3.1611 host connected to MS active directory. It is working normal for local and AD users. However in the logs, I see that NSS is throwing call to winbind to retrieve the groups for "root" user. I wonder why it does and what can be done to make it stop doing that. I believe it should do the lookup only for the domain/AD users. [2019/10/02

Hi! I got the following runtime error when I tried to use svm method with stepclass. Error in "colnames<-"(`*tmp*`, value = c("0", "1")) : attempt to set colnames on object with less than two dimensions I repeated the same sequence of statements but this time I used the classification function used in the example, i.e., "lda" and it worked fine