Hiya, thanks a lot for that Will (sorry spelt name wrong before!), think you're reply has almost got there...
If I dos2unix the file it works, if I use vi/m (what I normally use) or nano etc, it doesn't work (but will if I then dos2unix it again)?
SELinux I think is on permissive/targeted (I'm not too familiar with selinux as someone else set it up, but my understanding is that it should allow all, but log/audit it?).
Looks like thats it, but not sure still why its not saving it correctly?
Thanks, Ian
(lsattr shows ------------- logadmin btw)
On 9/25/06, Will McDonald wmcdonald@gmail.com wrote:
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. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos