search for: aaa2

...;- as.vector(t$int) f <- as.factor(t$group2) table(f) f 1 2 3 4 5 104940 104940 104940 104940 104940 dat <- cbind(as.data.frame(y),f) gc() summary(simtest(y ~ f, data=dat, type="Dunnett")) [1] "des <- model.matrix(ff, mf)" (Intercept) aaa1 aaa2 aaa3 aaa4 1 1 1 0 0 0 2 1 0 1 0 0 3 1 0 0 1 0 4 1 0 0 0 1 attr(,"assign") [1] 0 1 1 1 1 attr(,"contrasts") attr(,"contrasts")$aaa [1] "ct" [1] "gls <- rep(0,n...

Hi, I found a problem in the courier conversion script (courier-dovecot-migrate.pl). In some cases, it does not correctly preserve the order of POP3 UIDLs. Consider the following case, when courierpop3dsizelist contains: /2 9000 1327481629 AAA1:2,S 10000 21:1327481629 AAA2:2,S 10000 22:1327481629 AAA3:2,S 10000 23:1327481629 AAA4:2,S 10000 24:1327481629 AAA5:2,S 10000 25:1327481629 BBB11:2,S 10000 11:1327481629 BBB12:2,S 10000 12:1327481629 BBB13:2,S 10000 13:1327481629 BBB14:2,S 10000 14:1327481629 BBB15:2,S 10000 15:1327481629 and courierimapuiddb contains: 1 132...

...fs: unlinked 12 orphans Please let me know if you need other info and how bad this ''BUG'' is (i.e. do I need to go back from backup?). Also, can I tell which partition/btrfs pool was affected? gandalfthegreat:~# btrfs fi show Label: ''btrfs_pool2'' uuid: 2d17a045-aaa2-414f-9ef4-de671ae06fae Total devices 1 FS bytes used 219.75GB devid 1 size 872.51GB used 410.04GB path /dev/dm-1 Label: ''btrfs_pool1'' uuid: 873d526c-e911-4234-af1b-239889cd143d Total devices 1 FS bytes used 186.58GB devid 1 size 231.02GB used 231.02GB path /dev/dm-0...

...Dec 2 10:04:03 server rsyslogd-2177: imuxsock begins to drop messages from pid 5967 due to rate-limiting Dec 2 10:04:03 server setroubleshoot: SELinux is preventing /bin/ps from search access on the directory /proc/<pid>/stat. For complete SELinux messages. run sealert -l 0ef0c7a1-acb2-433a-aaa2-361cc95b6069 Dec 2 10:04:04 server setroubleshoot: last message repeated 2 times Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from getattr access on the directory /proc/<pid>. For complete SELinux messages. run sealert -l 58f859b0-7382-428e-81f0-3e85f66d79fc Dec 2 10...

...k begins to drop messages > from > > pid 5967 due to rate-limiting > > Dec 2 10:04:03 server setroubleshoot: SELinux is preventing /bin/ps from > > search access on the directory /proc/<pid>/stat. For complete SELinux > > messages. run sealert -l 0ef0c7a1-acb2-433a-aaa2-361cc95b6069 > > Dec 2 10:04:04 server setroubleshoot: last message repeated 2 times > > Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from > > getattr access on the directory /proc/<pid>. For complete SELinux > messages. > > run sealert -l 5...

...gt; >>> pid 5967 due to rate-limiting > >>> Dec 2 10:04:03 server setroubleshoot: SELinux is preventing /bin/ps > from > >>> search access on the directory /proc/<pid>/stat. For complete SELinux > >>> messages. run sealert -l 0ef0c7a1-acb2-433a-aaa2-361cc95b6069 > >>> Dec 2 10:04:04 server setroubleshoot: last message repeated 2 times > >>> Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps > from > >>> getattr access on the directory /proc/<pid>. For complete SELinux > >&gt...

...er rsyslogd-2177: imuxsock begins to drop messages from > pid 5967 due to rate-limiting > Dec 2 10:04:03 server setroubleshoot: SELinux is preventing /bin/ps from > search access on the directory /proc/<pid>/stat. For complete SELinux > messages. run sealert -l 0ef0c7a1-acb2-433a-aaa2-361cc95b6069 > Dec 2 10:04:04 server setroubleshoot: last message repeated 2 times > Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from > getattr access on the directory /proc/<pid>. For complete SELinux messages. > run sealert -l 58f859b0-7382-428e-81f0-3e...

...messages >> from >>> pid 5967 due to rate-limiting >>> Dec 2 10:04:03 server setroubleshoot: SELinux is preventing /bin/ps from >>> search access on the directory /proc/<pid>/stat. For complete SELinux >>> messages. run sealert -l 0ef0c7a1-acb2-433a-aaa2-361cc95b6069 >>> Dec 2 10:04:04 server setroubleshoot: last message repeated 2 times >>> Dec 2 10:04:04 server setroubleshoot: SELinux is preventing /bin/ps from >>> getattr access on the directory /proc/<pid>. For complete SELinux >> messages. >>>...

We are currently running libxml2-2.7.6-14.el6_5.2.x86_64 How far back would you suggest we go? would libxml2-2.7.6-14.el6_5.1.x86_64 be sufficient -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Daniel J Walsh Sent: 01 December 2014 15:10 To: CentOS mailing list Subject: Re: [CentOS] SEtroubleshootd Crashing I am not sure. I was

I am trying to run a new server with centos + xen using centos xen packages. After installation, we had to install a hardware raid card (areca) on the machine, and thus reload the os. It so happens the drivers shipped aren''t compatible with xen kernel, so i was forced to compile xen from source to compile areca drivers. Now with system running under compiled xen, i cannot boot my old