exec the script with softlimit from daemontools (very easy to use), or
exec with ulimit in the shell.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-ques
On Wednesday 20 May 2009 16:18:28 Kirk Strauser wrote:
> On May 20, 2009, at 7:00 AM, Mel Flynn wrote:
> > Check with top what the CPU time is, it's not the same as the wall
> > clock.
>
> Give me *some* credit. :-)
Sorry, haven't you heard? Financial crisis ;)
Are you sure cron respects login.con
On May 20, 2009, at 7:00 AM, Mel Flynn wrote:
Check with top what the CPU time is, it's not the same as the wall
clock.
Give me *some* credit. :-)
--
Kirk Strauser
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/
On Saturday 16 May 2009 19:27:22 Kirk Strauser wrote:
> www:\
>
> :cputime=300:\
> :tc=default:
>
> I've run "cap_mkdb /etc/login.conf" to make that live. Then, I used
> vipw to change www's class:
>
> www:*:80:80:www:0:0:World Wide Web Owner:/nonexistent:/usr/sbin/nologin
>
> H
I have a jail where the www user runs hourly cron jobs. On rare
occasion, these jobs get stuck in a seemingly infinite CPU loop - a
Python script calls Ghostscript and that child process never returns -
and I have to manually kill them. I'd like to use login.conf to set
resource limits so
