On 25/09/06, Ian mu mu.llamas@gmail.com wrote:
Hiya, thanks for that Wil, gives me some ideas. I notice the Bad file descriptor error in there, I've pasted the part there it starts to run it below (I'm only using touch as a basic test as other cron entries don't work, touch outside of cron works fine). I'm a bit clueless looking at the rest really though, is it definitely the bad file descriptor thats causing it, and any ideas why as its fine outside of cron?
read(6, "03 11 * * * /bin/touch /home/log"..., 4096) = 47 lseek(6, 47, SEEK_SET) = 47 read(6, "", 4096) = 0 read(6, "", 4096) = 0 close(6) = 0 munmap(0x2a9556c000, 4096) = 0 close(6) = -1 EBADF (Bad file descriptor)
It looks to me like crond is opening your crontab file OK, it appears to have read the line then choked on something.
Which editor are you using to edit the crontab? I wonder if it's something weird in the CR/LF sequences? You could try running dos2unix on /var/spool/cron/logadmin ? Could it possibly be SELinux? Have you got SELinux enabled?
I'd also check the extended attributes of all files and directories invoved in case something's out there (use "lsattr").
Will.