| 2007-08-18 15:07:12 |
Scott Kitterman |
None: statusexplanation |
You are going to need to provide a usable test case to replicate this. Preferably a minimal test case, but otherwise the code that leads to this problem. Otherwise, there is little a develper can do. |
There is a standard cron job that restarts syslogd on a daily basis. That appears to be what this is. I'm not sure how or if that might be relevant.
SIGTERM = Signal("TERM", 15, "Termination")
Looking at the man page for at, I find this:
"At and batch as presently implemented are not suitable when users are competing for resources. If this is the case for your site, you might want to consider another batch system, such as nqs."
It looks to me like you are running into this known limitation of at. What I would suggest is you either follow the recommendations in the man page and use a different batch system (that will be most robust I would guess) or adjust your cron job to make sure it doesn't run at the same time other cron jobs are running. |
|
