Linda Lofdahl schrieb: > I got the same error, so I removed the old logwatch and installed version > 7.3.6-1 (logwatch_7.3.6-1_all.deb from Debian Packages site), but I still get > the same error message: > > dolly:/tmp# logwatch --print > > zcat: stdout: No space left on device > system zcat failed: 256 at /usr/sbin/logwatch line 878. > > There's plenty of space left on the device:
Probably the file is removed when it can't be written fully. And 343 M is really not much. I recommend to change logwatch's TmpDir to something under home (at least for testing): echo "TmpDir = /home/something" > /etc/logwatch/conf/logwatch.conf Another solution is to not process the huge file that causes the error. You can configure that. > cd / ; df -h .. > Filesystem Size Used Avail Use% Mounted on > /dev/hda1 259M 136M 110M 56% / > tmpfs 502M 0 502M 0% /lib/init/rw > udev 10M 56K 10M 1% /dev > tmpfs 502M 0 502M 0% /dev/shm > /dev/hda9 173G 41G 124G 25% /home > /dev/hda8 373M 11M 343M 3% /tmp > /dev/hda5 4.6G 1.9G 2.5G 44% /usr > /dev/hda6 2.8G 2.4G 299M 89% /var > I need help with this since I run mail and web from this server and have some > problems with attacks. Of course the real (wishlist) bug is that logwatch actually needs so much space on disk. However there's a tradeoff: - Currently, logwatch is friendly to CPU and main memory, but not friendly to disk space. - If you make logwatch more friendly to disk space, you either need to make it more memory hungry or more CPU time hungry. Willi -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
