ACPI administration advocacy advocacy advocacy opinion alsa amarok apache apple apt aptitude archive audio audo authentication automount avi awk backup bash BIOS boot browser business bzip cache calendar calibre cdr cdrecord censorship commandline computerscience console convert cron cut database date debian degree design desktop development disk dpkg dvd economics education emacs email europe exim faad ffmpeg file files firefox firewall flash foss freedom ftp fun fuse git gnumeric graphics grep growisofs grub gtkpod gzip hardware hardware html icedove idiocy image imagemagick images installation ip iphone ipod iptables iso itunes ivman kde kernel keyboard knoppix lame laptop latex libreoffice linux locale lockin locking longlines lsof m4a microsoft mimetypes minitab mogrify mount mp3 mp4 mplayer multimedia music mysql network nfs nfs4 nmap openbox openfiles openoffice opinion opinion orgmode partition pdf pdftk perl php podcast politics pomodoro ports postgresql print printing privacy process programming rant remote rhythmbox rss rsync rxvt scp screengrab screenshot script scripting scsi security sed server services shell siteadmin sitenews sitesoftware skype skype slackware sound sox spam spreadsheet ssh statistics subversion sudo svk swap t23 t43 tar terminal tex text thinkpad thunderbird time timer timezone ubuntu udev upgrade usb usbmount users uuid versioncontrol vfat video vnc windows wine wordpress wordprocessing X40 xwindows xwindows youtube
Log management is one of those essential jobs that needs to be done, otherwise your logs just grow and grow and grow and before you know it you've got no space left on your hard disk.
That's why you need a utility like logrotate. It runs through your log files and compresses them. I've found though, that there can be problems. If one of logrotate's config files (stored in /etc/logrotate.d/ in Debian) relates to a missing daemon or there are some missing logs that logrotate tries to rotate, it can exit with an error. Then daemons running on the machine can crash. I've had this issue with mysql - logrotate removed the file 'mysql.log' and as a consequence the mysql daemon wouldn't restart.
The solution was simple: I read the emails that logrotate sends when it exits with an error and fixed whatever was the problem. Also, if you remove daemons from your machine make sure that logrotate's config files are fixed so that it doesn't try to handle the log files of daemons that no longer exist.
Logrotate is availble here