My scripts are not even near any document root. There's a whole
separate directory tree (for *all* CGI directories on the server)
that is ScriptAlias'd. I don't allow CGI for any user within
their doc root otherwise unsuspecting users would enable someone
to break into the server. The system de
Hello Brian,
On Friday, December 13, 2002 at 2:46:28 PM you wrote:
> I know about the per user quota settings. Is there anywhere to do a
> per domain quota capping? Eg. Cap the quota for the directory of the
> domain.
Make use of system quota.
Create a dedicated user for ea
If you use system quotas (as I do), then
install qmailadmin setuid root and it all works fine.
It will switch to the userid of the system account
that is specified in the users/assign file.
Brian
> Hello Ninad,
>
> On Friday, December 13, 2002 at 12:37:56 PM you wrote:
>
> >>> I know
Hello Ninad,
On Friday, December 13, 2002 at 12:37:56 PM you wrote:
>>> I know about the per user quota settings. Is there anywhere to do a
>>> per domain quota capping? Eg. Cap the quota for the directory of the
>>> domain.
>> Make use of system quota.
>> Create a dedicated user for each domain
Hello,
When I had tried a similar thing earlier, qmailadmin refused to work
probably due to change of user/group which expects vchkpw:vpopmail
Is there any workaround for this problem, other than using a separate
qmailadmin binary having identical permissions for every such domain
group?
Regards
Hello Neo,
On Friday, December 13, 2002 at 9:36:44 AM you wrote:
> I know about the per user quota settings. Is there anywhere to do a
> per domain quota capping? Eg. Cap the quota for the directory of the
> domain.
Make use of system quota.
Create a dedicated user for each domain you want to ha