Where's that damn....
I would like to use this opportunity to mention how annoying it its to try and debug a bug that doesn't manifest itself when run from the command line, but only when run every five minutes from crontab.
I went to bed early and slept for 3 odd hours, and then woke up and couldn't fall asleep again. That's why I'm debugging at 5:30 am. I probably should start considering trying again.
Oh yeah, happy birthday to Dilph.. And magic_trashman.. And snowyote soon too.. We're quite a January bunch here.
*faceslaps* OK, now I feel silly.. I'm adding in instrumentation to 1984, and was baffled by the fact that it was logging twice the runtime when run from crontab. The explanation is that I have 2 crontab entries, one for development and one for production, and when they're doing the exact same thing at the exact same time, it's bound to double the runtime.. Better offset them a bit. Just goes to show that I should go to bed.
I went to bed early and slept for 3 odd hours, and then woke up and couldn't fall asleep again. That's why I'm debugging at 5:30 am. I probably should start considering trying again.
Oh yeah, happy birthday to Dilph.. And magic_trashman.. And snowyote soon too.. We're quite a January bunch here.
*faceslaps* OK, now I feel silly.. I'm adding in instrumentation to 1984, and was baffled by the fact that it was logging twice the runtime when run from crontab. The explanation is that I have 2 crontab entries, one for development and one for production, and when they're doing the exact same thing at the exact same time, it's bound to double the runtime.. Better offset them a bit. Just goes to show that I should go to bed.