search for: decresing

...trix using function order, Some thing really odd: e.g. abc<-cbind(c(1,6,2),c(2,5,3),c(3,2,1))## matrix I want to sort if I do abc[ order(abc[,3]), increasing = TRUE] the result is correct [,1] [,2] [,3] [1,] 2 3 1 [2,] 6 5 2 [3,] 1 2 3 But if I want to sort in decresing order: abc[ order(abc[,3]), decreasing = TRUE] the result is wrong [,1] [,2] [,3] [1,] 2 3 1 [2,] 6 5 2 [3,] 1 2 3 Also if I use abc[ order(abc[,3]), increasing = FALSE] it returns nothing [1,] [2,] [3,] Why is that? Many thanks Yan [[alternative HTML version...

Hello all, I am trying out version 2.3RC3 but it seems it has the same bug as all versions before (including 2.2 KH9 which I used last) When trying to relay an on-demand stream with icecast and also limiting, I always find that icecast counts completely wrong. The first listener is not counted, but icecast connects to the master server, gets the stream and relays. If a second client

I've found the need to compute a version of order(x,y) where I want the sort order for *increasing* x and *decresing* y ... something we could imagine could be provided in the future as order(x,y, decreasing = c(FALSE, TRUE)) i.e., using a 'vectorized' decreasing argument. {No, I'm not volunteering right now!} I've found the following R-level solution and like to quiz you for more elegant /...

On Sun, 2005-09-18 at 18:07, Rene Gallati wrote: > Hello all, > > I am trying out version 2.3RC3 but it seems it has the same bug as all > versions before (including 2.2 KH9 which I used last) > > When trying to relay an on-demand stream with icecast and also limiting, > I always find that icecast counts completely wrong. The first listener > is not counted, but

...> allocation, in that case the VM resident memory size it is decreasing, > but it not decrease so much as it is expected, and it started to swap > out to host swap disk. The VM on idle state it has 32GB total memory > and 21GB free memory. And what I see the RSS size of the qemu is > decresing with 5-6GB. I fear you might be mis-interpreting what the balloon device actually does. It is a totally *manual* mechanism. You have booted the guest with 32GB set as maxmemory and currentmemory. So initially the guest will have its full 32GB available and no balloon driver activity will take pl...

...allocation, in that case the VM resident memory size it is decreasing, > but it not decrease so much as it is expected, and it started to swap > out to host swap disk. The VM on idle state it has 32GB total memory > and 21GB free memory. And what I see the RSS size of the qemu is > decresing with 5-6GB. I fear you might be mis-interpreting what the balloon device actually does. It is a totally *manual* mechanism. You have booted the guest with 32GB set as maxmemory and currentmemory. So initially the guest will have its full 32GB available and no balloon driver activity will take...

Hello friends I've problem with my Centos 4.3. On start some information: 1. serwer HP DL 380 x Intel(R) Xeon(TM) CPU 3.40GHz 2. RAM 4GB 3. HDD storage FC 4. kernel 2.6.9-34.0.2.ELsmp #1 SMP This serwer is working with another one (that some configuration) in RHEL cluster (locking by DLM), as a file serwer with samba-3.0.22. Samba have about 100 simultaneus sessions. Problem is with load

Hi, all. I just upgrade from 1.0.15 to 1.1.1 in a test box(RHEL 5.2, x86_64). after upgrade, i got this warning msg: ----8< ---- # /etc/init.d/dovecot restart Stopping Dovecot Imap: [ OK ] Starting Dovecot Imap: Warning: fd limit 1024 is lower than what Dovecot can use under full load (more than 1280). Either grow the limit or change