Hello, On Wed, 27 Feb 2008, A. Costa wrote: > If there was no update script or 'cron' job in 'swish++', I'd agree > with upstream.
There is no cron job in swish++. The cron job is setup by the programs
that make use of swish like "dwww". We may have need for a sharper
policy on what "cron" processes can do.
> But a system wide weekly update script is a Debian
> thing, and default package settings shouldn't overburden a system.
>
> If you don't have time to fix it, please just let it sit; that's
> what the 'wontfix' tag is for.
OK.
Your analysis of the cron problem is interesting. Perhaps someone
will implement a version of cron that does such analysis and makes
use of it.
Currently, the solutions available are:
(a) Every package that creates a cron job should set up
resource limits for this cron job using "ulimit" in a manner
similar to the use of "ulimit" in "rlimit". (Perhaps this
could be proposed as a policy requirement by a suitable
amendment of section 9.5 of Debian policy.)
This will limit the resources alloted by the system (via cron) to any
cron job.
(b) If there is reason to suspect that some file filtering
processes will use all the resources alloted to swish++, then
the user who involes "swish++" should use a script like
"rlimit".
This will limit the resources alloted by swish++ to the task of processing
any one file.
Regards,
Kapil.
--
signature.asc
Description: Digital signature
