Murray J. Root wrote: >On 06 Jul 2002 12:46:19 +0400 Borsenkow Andrej <[EMAIL PROTECTED]> >wrote: > >>� ���, 06.07.2002, � 12:27, Mattias Dahlberg �������: >> >>>On Fri, 5 Jul 2002, Todd Lyons wrote: >>> >>>>ls -l /etc/cron.daily >>>>ls -l /etc/cron.hourly >>>> >>>>Remove the msec link and you get rid of a small portion of the >>>>clobbering. Remove the slocate link and you get rid of a good bit of >>>>the clobbering. Remove the logrotate and you run out of disk space >>>>soon. It's up to you really. >>>> >>>Would it be a better idea to make the users who want slocate put it in >>>cron.dialy instead? And not have it there by default. >>> >> >>or put it generally - we need drakcron for easy configuration of cron >>tasks :-) >> > >Use Webmin - any easier and I'd feel stupid using it. :) > For the why? the answer is in the frogs. An ordinary frog goes "ribbit, ribbit" and a budfrog goes "bud ,,, Weis... Er", but a winforg goes "reboot, reboot, reboot"
Obviously these tasks have to be accomplished at intervals. Some are asking if the slocate and makewhatis can be done less frequently for a workstation install, and that is possible (move them from cron.daily to cron.weekly, for instance), perhaps as a default install measure for "recommended" installs. But before such a decision is made, how about a few cooker types making the move and reporting how many times they resorted to updatedb and makewhatis from a terminal out of frustration.. Especially those who ask why. That data to back a decision would be really helpful. Civileme
