Re: Post commit hook script: strange behavior

Am Montag, den 06.06.2005, 14:30 +0200 schrieb Nicolas Goutte:
> I mean especially the -t limit which limits the time used on the CPU. (Often
> for servers there are time limits, so that a process cannot bring down a
> server by an endless loop.)

I found a solution, which does not make me happy: the processes
(obviuosly) stopped because of whitespaces in the keyword list. The -0
option to xargs healed this.

Anyway, I am still wondering why this is a problem in a hook script, but
not from cron...

But the ulimit hint perhaps explains the behavior that scripts doing
much work invoked from post-commit run longer: the process limit is 2047
then, and unlimited otherwise. Could be an explanation (but I still
don't know why this occurs).

Thanks again for all hints.

regards,

-- 
Lutz Frommberger
SFB/TR 8 Spatial Cognition - Project R3-[Q-Shape]
Cognitive Systems Research Group, Universität Bremen
http://www.cosy.informatik.uni-bremen.de/staff/lutz/