Hi Andy,

this error is related to php settings in php.ini and not to NetBSD 
process settings.

Since php 4 there is a php function call to extend the maximum 
execution time for a script.
Please have a look into the php documentation.

regs
Tobias

On Mon, 13 Jun 2005 14:07:08 +0000, Andy Ruhl wrote:
> I got this error trying to do something with a PHP ap from a web front
> end on a stock 2.0.2 i386 machine:
> 
> [client x.x.x.x] PHP Fatal error:  Maximum execution time of 30
> seconds exceeded in /someurl/gallery/save_photos.php on line 163,
> referer: http://some.url/gallery/save_photos.php
> 
> I'm not sure why I would get this? 
> 
> For a normal user, the cpu time limit is set to unlimited. I'm not
> sure what exact sysctl I need to look at, but this is what I have if I
> just grep on limit (excluding non proc stuff):
> 
> proc.curproc.rlimit.cputime.soft = unlimited
> proc.curproc.rlimit.cputime.hard = unlimited
> proc.curproc.rlimit.filesize.soft = unlimited
> proc.curproc.rlimit.filesize.hard = unlimited
> proc.curproc.rlimit.datasize.soft = 134217728
> proc.curproc.rlimit.datasize.hard = 1073741824
> proc.curproc.rlimit.stacksize.soft = 2097152
> proc.curproc.rlimit.stacksize.hard = 33554432
> proc.curproc.rlimit.coredumpsize.soft = unlimited
> proc.curproc.rlimit.coredumpsize.hard = unlimited
> proc.curproc.rlimit.memoryuse.soft = 450527232
> proc.curproc.rlimit.memoryuse.hard = 450527232
> proc.curproc.rlimit.memorylocked.soft = 150175744
> proc.curproc.rlimit.memorylocked.hard = 450527232
> proc.curproc.rlimit.maxproc.soft = 160
> proc.curproc.rlimit.maxproc.hard = 532
> proc.curproc.rlimit.descriptors.soft = 512
> proc.curproc.rlimit.descriptors.hard = 1772
> 
> I'm reading the man page for login.conf, but I don't actually have a
> login.conf, so I don't know if I need to create one or something. But
> then again, this looks like cpu time is unlimited, isn't it? I run
> setiathome for 1 user, and there's no problem with that, it runs
> forever.
> 
> Andy
>