[vchkpw] Re: Patch to disable vusaged
Tonix (Antonio Nati) wrote: I did not imagine vusaged was so intrusive! Is should be completely disabled if not needed. Tonino -- Matt, Is there some sort of specification documentation for vusaged that describes how it works? If there is, I think it would be useful to have it published so that it can be scrutinized by the community. Better to get things worked out up front than to confront them in the debugging stage. -- -Eric 'shubes' !DSPAM:4a9fe92532714008716074!
Re: [vchkpw] Re: Patch to disable vusaged
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Shubert wrote: Is there some sort of specification documentation for vusaged that describes how it works? If there is, I think it would be useful to have it published so that it can be scrutinized by the community. Better to get things worked out up front than to confront them in the debugging stage. I don't have a document prepared, however it's relatively simple. In the most simple terms, all it does is look up every user under vpopmail, and count how much storage they're using. That is how it calculates user usage. To calculate domain usage, it adds up all the users' storage counts. There are a great deal of efficiencies added, of course. Constantly polling the disk would be extremely inefficient. It's also meant to be extremely fault tolerant, meaning, if vusaged isn't running, or the client API fails, delivery does not cease, and is not delayed in any noticable manner. I suppose the reason there is no document explaining this, is because the general idea is very simple, and the vusaged configuration file explains many of the efficiencies via it's configurable options. Was there any specific topic you were interested in? I'd be happy to provide whatever information you're looking for. - -- /* Matt Brookings m...@inter7.com GnuPG Key FAE0672C Software developer Systems technician Inter7 Internet Technologies, Inc. (815)776-9465 */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqf63sACgkQIwet2/rgZyzdzgCfdBAjyoumOT5WTZ0XMrA9dCIA dcYAoIlo5SBhAKkxaS01a7knGriEBG/i =/BdW -END PGP SIGNATURE-
[vchkpw] Re: Patch to disable vusaged
Matt Brookings wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric Shubert wrote: Is there some sort of specification documentation for vusaged that describes how it works? If there is, I think it would be useful to have it published so that it can be scrutinized by the community. Better to get things worked out up front than to confront them in the debugging stage. I don't have a document prepared, however it's relatively simple. In the most simple terms, all it does is look up every user under vpopmail, and count how much storage they're using. That is how it calculates user usage. To calculate domain usage, it adds up all the users' storage counts. There are a great deal of efficiencies added, of course. Constantly polling the disk would be extremely inefficient. It's also meant to be extremely fault tolerant, meaning, if vusaged isn't running, or the client API fails, delivery does not cease, and is not delayed in any noticable manner. I suppose the reason there is no document explaining this, is because the general idea is very simple, and the vusaged configuration file explains many of the efficiencies via it's configurable options. Was there any specific topic you were interested in? I'd be happy to provide whatever information you're looking for. - -- No, that pretty well sums it up. I should have a look at the configuration file. I don't expect that'll happen for me until ldap on 5.5 is ready for testing though. ;) I was just a little concerned about Tonix's comments. We'll see what he has to say. I'm confident you'll do what's best. Thanks for the great work. -- -Eric 'shubes' !DSPAM:4a9fee7e32711532716672!
