Question-and-Answer Resource for the Building Energy Modeling Community
 | 1 | initial version |
Your rpict processes are being killed by the system, somehow. The only time rpict will report a signal is when it receives one, and it does what a process should do by politely exiting. Pfilt is then left to clean up after, and finds the images short of the length they claim. Simply re-running the rad program should finish up the renderings where they left off, provided the processes don't get killed again.
You need to find out why your processes are being terminated. One possibility is that the system is running low on memory, so decides to kill its larger processes. Another possibility is that the file size is being exceeded during rendering, though this seems unlikely as your images are not that big. Check out what the limits are in your shell "ulimit" command ("limit" in C-shell). Also, make sure that huponexit is not set, and/or you have run "disown -h PID" on the process, so that it won't get killed when the shell dies. (These are bash-only commands -- I don't think the C-shell kills it's children so eagerly.)
Let us know what you find out!
| | 2 | No.2 Revision |
Your rpict processes are being killed by the system, somehow. The only time rpict will report a signal is when it receives one, and it does what a process should do by politely exiting. Pfilt is then left to clean up after, and finds the images short of the length they claim. Simply re-running the rad program should finish up the renderings where they left off, provided the processes don't get killed again.
You need to find out why your processes are being terminated. One possibility is that the system is running low on memory, so decides to kill its larger processes. Another possibility is that the file size is being exceeded during rendering, though this seems unlikely as your images are not that big. Check out what the limits are in your shell "ulimit" command ("limit" in C-shell). Also, make sure that huponexit is not set, and/or you have run "disown -h PID" on the process, so that it won't get killed when the shell dies. (These are bash-only commands -- I don't think the C-shell kills it's its children so eagerly.)
Let us know what you find out!
