As far as I can tell, these errors are (minor) mandrake packaging
errors, and have nothing to do with file/disk corruption (as Civileme
suggested). I also get the identical errors about tixwish and rec, and
in addition I get one on rdump and rrestore. Looking into the errors I
get after running the /etc/cron.weekly/makewhatis.cron:
1) Read file error: ./rec.1 No such file or directory
"file `locate rec.1`" gives:
/usr/man/man1/rec.1: broken symbolic link to /var/tmp/sox-root//usr/man/man1/play.1
2) bzcat: ./tixwish.1.bz2 is not a bzip2 file.
It turns out that tixwish.1.bz2 has a bz2 extension, but is not
compressed at all; it should probably be renamed to tixwish.1
3) bzcat: Can't open input file ./rdump.8.bz2: No such file or directory.
bzcat: Can't open input file ./rrestore.8.bz2: No such file or directory.
These are (dangling) symlinks into /usr/man/man8/{dump,restore}.8.
However, the target files are compressed using bzip2, and thus have a
.bz2 extension.
I suspect that the errors you got for fetchmailconf and efence have
similar causes. I verified the Mdk 6.1 rpms, and these errors are
present in them. Somebody at Mandrake should fix the man pages in
these rpms...
-- Alex
| [EMAIL PROTECTED] wrote:
|
| > Anyone know what might be causing this error from cron.weekly? I havent
| > made any changes to cron so I dont see why it would be failing.
| >
| > To: [EMAIL PROTECTED]
| > Subject: Cron <root@moon> run-parts /etc/cron.weekly
| > X-Cron-Env: <SHELL=/bin/bash>
| > X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
| > X-Cron-Env: <MAILTO=root>
| > X-Cron-Env: <HOME=/>
| > X-Cron-Env: <LOGNAME=root>
| >
| > bzcat: ./tixwish.1.bz2 is not a bzip2 file.
| > bzcat: Can't open input file ./fetchmailconf.1.bz2: No such file or directory.
| > Read file error: ./rec.1 No such file or directory
| > bzcat: ./efence.3.bz2 is not a bzip2 file.
