search for: ms4

...the quota informaiton: [...] 2 getquotaroot INBOX * QUOTAROOT "INBOX" "" * QUOTA "" (STORAGE 880 5) 2 OK Getquotaroot completed. [...] When I have a setup with quotas only in the database, everything works as expected and deliver denies the message: Sep 5 21:50:14 ms4 deliver(postfach at email5.former03.local): msgid=<20070905195014.9D874239C007 at ms4.srv.hoster03.de>: save failed to INBOX: Quota exceed ed Sep 5 21:50:14 ms4 deliver(postfach at email5.former03.local): msgid=<20070905195014.9D874239C007 at ms4.srv.hoster03.de>: Rejected: Quo...

...components to use and how to order them in the network path from client to mail store. If I have say 1,000 users, all stored in MySQL (or LDAP) and have 4 mail stores, configured into 2, 2 node pods. MS1 and MS2 are pod1 and are configured with replication (dsync) and host users 0-500. MS3 and MS4 are pod2 and are configured with replication between them and host users 501-1000. Ideally the active connections in pod1 would be split 50/50 between MS1 and MS2. When maintenance is performed obviously all active connections/users would be moved to the other node in the pod and then rebalanced...

...path from client to mail store. >> >> >> If I have say 1,000 users, all stored in MySQL (or LDAP) and have 4 mail stores, configured into 2, 2 node pods. >> >> >> MS1 and MS2 are pod1 and are configured with replication (dsync) and host users 0-500. MS3 and MS4 are pod2 and are configured with replication between them and host users 501-1000. Ideally the active connections in pod1 would be split 50/50 between MS1 and MS2. When maintenance is performed obviously all active connections/users would be moved to the other node in the pod and then rebalanced...

...rder them in the network path from client to mail store. > > > If I have say 1,000 users, all stored in MySQL (or LDAP) and have 4 mail stores, configured into 2, 2 node pods. > > > MS1 and MS2 are pod1 and are configured with replication (dsync) and host users 0-500. MS3 and MS4 are pod2 and are configured with replication between them and host users 501-1000. Ideally the active connections in pod1 would be split 50/50 between MS1 and MS2. When maintenance is performed obviously all active connections/users would be moved to the other node in the pod and then rebalanced...

...l store. >>> >>> >>> If I have say 1,000 users, all stored in MySQL (or LDAP) and have 4 mail stores, configured into 2, 2 node pods. >>> >>> >>> MS1 and MS2 are pod1 and are configured with replication (dsync) and host users 0-500. MS3 and MS4 are pod2 and are configured with replication between them and host users 501-1000. Ideally the active connections in pod1 would be split 50/50 between MS1 and MS2. When maintenance is performed obviously all active connections/users would be moved to the other node in the pod and then rebalanced...

...;> >>>> >>>> If I have say 1,000 users, all stored in MySQL (or LDAP) and have 4 mail stores, configured into 2, 2 node pods. >>>> >>>> >>>> MS1 and MS2 are pod1 and are configured with replication (dsync) and host users 0-500. MS3 and MS4 are pod2 and are configured with replication between them and host users 501-1000. Ideally the active connections in pod1 would be split 50/50 between MS1 and MS2. When maintenance is performed obviously all active connections/users would be moved to the other node in the pod and then rebalanced...

...ata to draw a phylogenetic tree, so that I can infer which ms was copied from which. The error presence/absence is coded in binary format. The plan is to use a maximun parsimony tree approach. The data looks like this toy example: "ms1" "ms2" "ms3" "ms4" "err1" 0 1 0 0 "err2" 0 0 1 1 "err3" 1 1 0 0 "err4" 0 0 0 1 "err5" 1 1 1 0 "err6" 1 1 0 1 "err7" 0 1...

OK, so there's a bunch of stuff in here. The geometry stuff is based on the work started by Bryan Cain and Christoph Bumiller. Patches 01-12: Add support for geometry shaders and fix related issues Patches 13-14: Make it possible for fb clears to operate on texture attachments with an explicit layer set (as is allowed in gl 3.2). Patches 15-17: Make ARB_texture_multisample work

Hello list. I'm trying to rebuild the 2.6.9.67.0.20.EL kernel, but it fails even without modifications. How did I try it? Created a (non-root) build environment (not a mock ) Installed the kernel.scr.rpm and did a rpmbuild -ba --target=`uname -m` kernel-2.6.spec 2> prep-err.log | tee prep-out.log The build failed at the end: Processing files: kernel-xenU-devel-2.6.9-67.0.20.EL Checking