On 16 Apr, Louis Selvon wrote:
> >That sounds a little like /usr/bin/crontab is not executable due to
> problems in shared libraries or ldconfig version.
>
> >What happens if you say:
>
> > ldd /usr/bin/crontab
>
> *** Output follows:
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> [root@ensim admin]# ldd /usr/bin/crontab
> libc.so.6 => /lib/i686/libc.so.6 (0x4001e000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
That looks good and correct.
> >You could also try:
>
> > strace /usr/bin/crontab -l
>
> >and see what kind of errors happen near the end.
>
> **** Output follows. This is a long one, and I do not understand any of it.
[...]
> send(3, "<78>Apr 16 19:34:33 crontab[8073"..., 54, 0) = 54
> rt_sigaction(SIGPIPE, {SIG_DFL}, NULL, 8) = 0
> open("cron/root", O_RDONLY) = -1 ENOENT (No such file or
> directory)
> write(2, "no crontab for root\n", 20no crontab for root
> ) = 20
> _exit(1) = ?
Odd. That isn't the error being reported from bash, which from memory
was: "/bin/bash: /usr/bin/crontab: file not found"
Anyway, it sounds very like the crontab -e did not in fact create a
crontab file for root. Weird!
luke
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
