----------
>
> At this point, I just want to get rid of the DB2 message! Thanks a lot ....
> to anyone who can point to a solution.
>
> Jacqueline Michell
>
Jacqueline,
Let us start with your slocate problem first. Did you upgrade it to a version beyond
2.2-6mdk? I did and had the same problems. But if it isn't that, let us look at your
/etc/updatedb.conf which is basically what your mail is spitting out to you about:
slocate: this is not a valid slocate database:
/var/lib/slocate/slocate.db
--------------------------
slocate.db is a list of *.dll (obviously Windows files) Why?????
Another file (/usr/bin/slocate.cron) is as follows:
"udf,nfs,smbfs,ncpfs,proc,devpts,iso9660,usvdevfs" -e
"/tmp,/var/tmp,/usr/tmp,/afs,/net"
--------------------------
The following files (/var/spool/cron/ directory) consist of numbers that
don't seem to follow the date and time format:
cron.daily -- 20010131
cron.weekly -- 20010127
cron.monthly -- 20010127
--------------------------
Let us break this message down into three parts, first.
slocate: this is not a valid slocate database:
/var/lib/slocate/slocate.db
--------------------------
I have the same configuration and location as you but when I tried to access an
updated slocate rpm off of Mandrake-devel (slocate-2.4-1) I received the same errors.
Second part:
slocate.db is a list of *.dll (obviously Windows files) Why?????
Why? Because it is accessing your windows partition as well as any other partition
filetype that is not being excluded like these: ("*****" will wrap the filetypes I am
referring)
Another file (/usr/bin/slocate.cron) is as follows:
****"udf,nfs,smbfs,ncpfs,proc,devpts,iso9660,usvdevfs"**** -e
"/tmp,/var/tmp,/usr/tmp,/afs,/net"
The second line are the directories that your slocate database is ignoring as well.
You wouldn't want to bloat your database with temp files would you? In other words,
that file is good. Next:
The following files (/var/spool/cron/ directory) consist of numbers that
don't seem to follow the date and time format:
cron.daily -- 20010131
cron.weekly -- 20010127
cron.monthly -- 20010127
--------------------------
I have a link for you:
http://mandrakeuser.org/admin/acron2.html
that should teach you how to properly include and configure jobs for your anacron.
Your last problem, DB2, is not really a problem unless...
This is simply saying that you have one, some or all of the following database
managers installed on your computer and you have not created any database tables or
anything for your database manager. If you don't plan on using these database
managers, I recommend that you remove them from your system with the following command:
rpm -e [database manager name here]
If you do plan on using any of them but you have not "got around to it", turn it off.
It is okay, because the database manager(s) are still there. They're just not included
in your cron jobs. So then you won't receive unnecessarily redundant messages from
anacron in your mail que. It is a problem on the other hand if you have put one
together and installed it into a database manager and you have only one running at
starttime and that is the one you have put your database tables. (unlikely, because
you would have more error messages other than just a missing DB key)
Cheers,
-- Al
__________________________________________________________________
Get your own FREE, personal Netscape Webmail account today at
http://webmail.netscape.com/
