You are not on a shared server, and you haven't installed any "monitor" daemon that kills a process after x-minutes, x-minutes of CPU, or something similar?
Usually, in fact in all the cases that I remember coming up, whenever a process is terminated at relatively the same place (especially if it's unit-time) it's turned out to be the above.
If you are doing it via HTTP:, your server may be timing out the nph- connection, and you need to run the script via telnet. But, running via telnet will not get around the daemon killer mentioned above.
If it's _not_ one of these problems, I really want to know to add to the list. Checking my notes, the only other thing that killed a process was running out of disc space, but that caused other problems -- and you wouldn't have been able to keep developing (unless your web pages are built on another partition/device? from where the scripts are run)
As noted -- the new links has 3 build options in the admin (none connected yet) for build changed, build staggered and build all.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
Usually, in fact in all the cases that I remember coming up, whenever a process is terminated at relatively the same place (especially if it's unit-time) it's turned out to be the above.
If you are doing it via HTTP:, your server may be timing out the nph- connection, and you need to run the script via telnet. But, running via telnet will not get around the daemon killer mentioned above.
If it's _not_ one of these problems, I really want to know to add to the list. Checking my notes, the only other thing that killed a process was running out of disc space, but that caused other problems -- and you wouldn't have been able to keep developing (unless your web pages are built on another partition/device? from where the scripts are run)
As noted -- the new links has 3 build options in the admin (none connected yet) for build changed, build staggered and build all.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
