I did a "locate" today and got a warning message that the updatedb database was more than 8 days old. I found the problem: the file /etc/cron.daily/aaa_base_updatedb has the following test: if [ -n "$RUN_UPDATEDB" -a "$RUN_UPDATEDB" = "yes" -a \ -x /usr/bin/updatedb ] ; then Notice that it is looking for updatedb in /usr/bin. On my SuSE 7.0 system this is in /usr/sbin. Is this a problem in the SuSE 7.0 distribution or have I somehow messed this up? (I can't imagine how I could have done this.) Is it possible that other executables have moved and that other, similar, scripts may not be working? P.S. I fixed it by putting a soft link in /usr/bin. -- ____________________________________________________________________ Robert Paulsen paulsen@texas.net
On Saturday 06 January 2001 05:41, Robert C. Paulsen Jr. wrote:
I did a "locate" today and got a warning message that the updatedb database was more than 8 days old.
I found the problem: the file /etc/cron.daily/aaa_base_updatedb has the following test:
if [ -n "$RUN_UPDATEDB" -a "$RUN_UPDATEDB" = "yes" -a \ -x /usr/bin/updatedb ] ; then
Notice that it is looking for updatedb in /usr/bin. On my SuSE 7.0 system this is in /usr/sbin.
Is in /usr/bin on Suse 7 here...
Is this a problem in the SuSE 7.0 distribution or have I somehow messed this up? (I can't imagine how I could have done this.) Is it possible that other executables have moved and that other, similar, scripts may not be working?
P.S. I fixed it by putting a soft link in /usr/bin.
participants (2)
-
Cliff Sarginson
-
Robert C. Paulsen Jr.