-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Thursday, March 13, 2008 10:42 AM -0400 Shelley Waltz <shwaltz@xxxxxxxxxxxxxxxx> wrote: > I have a cyrus-2.2.3 installation with quotas appearing as flat files > in /var/lib/imap/quota/(a-z)/user.* Each file has 2 lines, the quota > and the current useage. I process these files to generate quota warnings > for users in advance of reaching their limit. In the imapd.conf(5) man > page for this distribution, there is no configuration choice for > quota_db . > > In my new 2.3.7 RHAS5 distribution, quota_db choices are > quotalegacy(default), > flat,berkeley,berkeley-hash,skiplist. What is quotalegacy - is it what I > have in my 2.2.3 distribution? How is this different from flat? > > confused, > S > Someone may correct me if I'm wrong here, but I think this is right. I'd need to play with a test server to confirm, though. The 'quotalegacy' format is indeed what you're using now. It's the tree-structure, one-file-per-user quota format. The other formats now available are formats for a single, unified database file for all quotas. If you choose flat, I would expect that you'd get a single plain text file with all user quotas in it. Likewise skiplist or the berkeley variants would result in a single database file in those formats. -paul - -- Paul D. Engle | Rice University Sr. Systems Adminstrator, RHCE | Information Technology - MS119 713-348-4702 | PO Box 1892 pengle@xxxxxxxx | Houston, TX 77251-1892 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) iD8DBQFH2W6WCpkISWtyHNsRAnabAKDv827QhzNa45mqHF7Jlt7cN4JokACdH4/E d14ZWuTjw7X0NgZPBIHaAnQ= =PAQO -----END PGP SIGNATURE----- ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
