XCD-Roast works again after the latest online update. JDL -- Non enim propter gloriam, diuicias aut honores pugnamus set propter libertatem solummodo quam Nemo bonus nisi simul cum vita amittit.
Francis Allouchery
XCD-Roast works again after the latest online update.
Yes, SuSE have put new updated Imlib on line.
Yepp, after I fixed the brown paper bag bug introduced with my security fix that led to the failure in the first place :( Philipp
Having only installed SuSE 8.0 a few days ago, I was dismayed when I found that the "locate" command seemed to have disappeared. That's such a basic and useful command that I couldn't believe it was gone. A more careful reading of the SuSE manual revealed that it's no longer installed by default, but can be optionally installed by Yast2 (it's hidden in the "Basic" section as "findutils-locate"). The reason for no longer installing it by default I assume is because of the big performance hit you take when the daily "updatedb" command runs to update the database that "locate" needs. True, I've always found it annoying when performance crawls to a near halt when "updatedb" starts running just as I was doing something important. It runs as a daily cron job - the solution is to cancel the cron job and run "updatedb" whenever you feel the need to update. I moved the script file "updatedb" from /etc/cron.daily to /root, and all is well.
Le Jeudi 30 Mai 2002 05:44, Robert Storey a écrit / wrote:
Having only installed SuSE 8.0 a few days ago, I was dismayed when I found that the "locate" command seemed to have disappeared. That's such a basic and useful command that I couldn't believe it was gone. A more careful reading of the SuSE manual revealed that it's no longer installed by default, but can be optionally installed by Yast2 (it's hidden in the "Basic" section as "findutils-locate").
The reason for no longer installing it by default I assume is because of the big performance hit you take when the daily "updatedb" command runs to update the database that "locate" needs.
Another reason is maybe the number of posts to SuSE-lists from users who wanted to known who was this mysterious user 'nobody' who was each day using their computers...
True, I've always found it annoying when performance crawls to a near halt when "updatedb" starts running just as I was doing something important. It runs as a daily cron job - the solution is to cancel the cron job and run "updatedb" whenever you feel the need to update. I moved the script file "updatedb" from /etc/cron.daily to /root, and all is well.
Or move it to cron.weekly to let it do its job on a weekly basis. Francis
participants (4)
-
Francis Allouchery -
John Lamb -
Philipp Thomas -
Robert Storey