On Saturday, October 11, 2003, at 03:36 PM, Jochen Schug wrote:
Tom Collins wrote:
On Saturday, October 11, 2003, at 07:07 AM, Jochen Schug wrote:
An example to illustrate what I mean:
$> vmoddomlimits -Q 100M -q 20M example.com
results in a 100 byte quota for domain example.com, and 20 byte
d
Tom Collins wrote:
On Saturday, October 11, 2003, at 07:07 AM, Jochen Schug wrote:
An example to illustrate what I mean:
$> vmoddomlimits -Q 100M -q 20M example.com
results in a 100 byte quota for domain example.com, and 20 byte
default quota for users.
The current development builds parse
On Saturday, October 11, 2003, at 07:07 AM, Jochen Schug wrote:
An example to illustrate what I mean:
$> vmoddomlimits -Q 100M -q 20M example.com
results in a 100 byte quota for domain example.com, and 20 byte
default quota for users.
The current development builds parse the -q option properly,
Hi,
I noticed that vmoddomlimits doesn't care about a trailing 'M' or 'K'
when specifing quotas... Instead of complaining that there's an unknown
character in the quota, it silently ignores it. I ended up with a domain
with 100 byte quota and 20 byte per-user quota, and only noticed it from
th