search for: incommensur

Hmm. Chuck: I don't see how this example represents incomplete/incommensurate recycling. Doesn't TRUE replicate from length-1 to length-3 in this case (mat[c(TRUE,FALSE),2] would be an example of incomplete recycling)? William: clever, but maybe too clever unless you really need the speed? (The clever way is 8 times faster in the following case ...) x <- rep(1,1e...

Sorry if this has been covered here somewhere in the past, but ... Does anyone know why logical vectors are *silently* recycled, even when they are incommensurate lengths, when doing logical indexing? This is as documented: For ?[?-indexing only: ?i?, ?j?, ?...? can be logical vectors, indicating elements/slices to select. Such vectors are recycled if necessary to match the corresponding extent. but IMO weird: > x <- c(TRU...

...g the idmap.ldb. That works. >> After adding zum users the uid and gid begin to differ again. I read >> that it is not recommended to run a DC as a fileserver but in my case > >> it's not really an option. It's a network of twelve clients, so four >> servers are incommensurate to this amount of clients. >> I searched regarding sssd, because my nsswitch.conf also has it. But >> how do I have to configure it all? >> My actual nsswitch.conf provides the following: >> passwd: files sss >> shadow: files sss >> group: files...

Dear all, Is there any standard statistical terminology describing the points beyond a confidence region? Obviously, the "outlier" is improper here. Please help me if you happens have the info. Thanks you very much for your kindly help. Best wishes, Zhiqiu [[alternative HTML version deleted]]

...the advice of copying the idmap.ldb. That works. > After adding zum users the uid and gid begin to differ again. I read > that it is not recommended to run a DC as a fileserver but in my case > it's not really an option. It's a network of twelve clients, so four > servers are incommensurate to this amount of clients. > I searched regarding sssd, because my nsswitch.conf also has it. But > how do I have to configure it all? > My actual nsswitch.conf provides the following: > passwd: files sss > shadow: files sss > group: files sss > services: fil...

...ks. >> After adding zum users the uid and gid begin to differ again. >> I read that it is not recommended to run a DC as a fileserver >> but in my case it's not really an option. It's a network of >> twelve clients, so four servers are incommensurate to this >> amount of clients. I searched regarding sssd, because my >> nsswitch.conf also has it. But how do I have to configure it >> all? My actual nsswitch.conf provides the following: passwd: >> files sss shadow: files sss group: files...

But will this idmap.ldb change work for upcoming new users or groups so that uid/gid will not be different? The wiki tells us about built-in groups. Those have the right ids. Am 9. Dezember 2014 23:03:44 MEZ, schrieb Rowland Penny <rowlandpenny at googlemail.com>: >On 09/12/14 21:07, Tim wrote: >> Hello all, >> >> I have a fresh install of two CentOS 7 machines. On

...ks. After adding zum users the uid and gid >> begin to differ again. I read that it is not recommended to >> run a DC as a fileserver but in my case it's not really an >> option. It's a network of twelve clients, so four servers are >> incommensurate to this amount of clients. I searched >regarding >> sssd, because my nsswitch.conf also has it. But how do I have >> to configure it all? My actual nsswitch.conf provides the >> following: passwd: files sss shadow: files sss group: files >>...

...ap.ldb. That works. > After adding zum users the uid and gid begin to differ again. > I read that it is not recommended to run a DC as a fileserver > but in my case it's not really an option. It's a network of > twelve clients, so four servers are incommensurate to this > amount of clients. I searched regarding sssd, because my > nsswitch.conf also has it. But how do I have to configure it > all? My actual nsswitch.conf provides the following: passwd: > files sss shadow: files sss group: files sss services: fi...

Hello, I have problem running the histogram function "hist". The area under the histogram is much lower than 1. Could anyone tell me what the problem is? Thanks, (The total number of observation is 992 (close to 1000), so the probability that 0<Y1<35 is approximately 0.277) miao rm(list=ls()) par(mfrow=c(1, 1)) Y <- cbind(matrix(35*0.5,1,277), matrix(35*1.5, 1, 146),

...id >>> and gid begin to differ again. I read that it is not >>> recommended to run a DC as a fileserver but in my case >>> it's not really an option. It's a network of twelve >>> clients, so four servers are incommensurate to this >>> amount of clients. I searched regarding sssd, because my >>> nsswitch.conf also has it. But how do I have to >configure >>> it all? My actual nsswitch.conf provides the following: >>> passwd: files...

...ap.ldb. That works. After adding zum users the uid and gid > begin to differ again. I read that it is not recommended to > run a DC as a fileserver but in my case it's not really an > option. It's a network of twelve clients, so four servers are > incommensurate to this amount of clients. I searched regarding > sssd, because my nsswitch.conf also has it. But how do I have > to configure it all? My actual nsswitch.conf provides the > following: passwd: files sss shadow: files sss group: files > sss services: fi...

...zum users the uid >> and gid begin to differ again. I read that it is not >> recommended to run a DC as a fileserver but in my case >> it's not really an option. It's a network of twelve >> clients, so four servers are incommensurate to this >> amount of clients. I searched regarding sssd, because my >> nsswitch.conf also has it. But how do I have to configure >> it all? My actual nsswitch.conf provides the following: >> passwd: files sss shadow: files s...

...> differ again. I read that it is not recommended to >>>> run a DC as a fileserver but in my case it's not >>>> really an option. It's a network of twelve clients, >>>> so four servers are incommensurate to this amount >of >>>> clients. I searched regarding sssd, because my >>>> nsswitch.conf also has it. But how do I have to >>>> configure it all? My actual nsswitch.conf provides >>>>...

...>>> recommended to run a DC as a fileserver but in >>>>> my case it's not really an option. It's a >>>>> network of twelve clients, so four servers are >>>>> incommensurate to this amount of clients. I >>>>> searched regarding sssd, because my >>>>> nsswitch.conf also has it. But how do I have >to >>>>> configure it all? My actual nsswitch.conf >>>&g...

...to >>> differ again. I read that it is not recommended to >>> run a DC as a fileserver but in my case it's not >>> really an option. It's a network of twelve clients, >>> so four servers are incommensurate to this amount of >>> clients. I searched regarding sssd, because my >>> nsswitch.conf also has it. But how do I have to >>> configure it all? My actual nsswitch.conf provides >>> the following: p...

...is not >>>> recommended to run a DC as a fileserver but in >>>> my case it's not really an option. It's a >>>> network of twelve clients, so four servers are >>>> incommensurate to this amount of clients. I >>>> searched regarding sssd, because my >>>> nsswitch.conf also has it. But how do I have to >>>> configure it all? My actual nsswitch.conf >>>>...

...recommended to run a DC as a fileserver but in >>>>>> my case it's not really an option. It's a >>>>>> network of twelve clients, so four servers are >>>>>> incommensurate to this amount of clients. I >>>>>> searched regarding sssd, because my >>>>>> nsswitch.conf also has it. But how do I have >> to >>>>>> configure it all? My actual nsswitch...

...t;>> begin to differ again. I read that it is not >>>>>> recommended to run a DC as a fileserver but in >>>>>> my case it's not really an option. It's a >>>>>> network of twelve clients, so four servers are >>>>>> incommensurate to this amount of clients. I >>>>>> searched regarding sssd, because my >>>>>> nsswitch.conf also has it. But how do I have >> to >>>>>> configure it all? My actual nsswitch.conf >>>>>> provides the following: passwd:...