Hide Forgot
Description of Problem: tmpwatch blows up on 18Gb files error: failed to lstat /tmp/plugtmp/terahertz4.tif: Value too large for defined data type Version-Release number of selected component (if applicable): tmpwatch-2.7.1-1 How Reproducible: 100% Steps to Reproduce: 1. put an 18 gigabyte file in /tmp 2. run tmpwatch via cron 3. read root's email Actual Results: Date: Tue, 27 Nov 2001 04:02:42 -0500 From: Cron Daemon <root@zod.capslock.lan> To: root@zod.capslock.lan Subject: Cron <root@zod> run-parts /etc/cron.daily /etc/cron.daily/tmpwatch: error: failed to lstat /tmp/plugtmp/terahertz4.tif: Value too large for defined data type Expected Results: tmpwatch treating the file like any other file, and hopefully removing that huge beast. Additional Information: No, I am not insane. I do not usually have 18Gb files laying around. ;o) Mozilla created this beast when trying to display an 8Mb TIFF image. It somehow went berzerk and my machine almost had a kernel panic due to a shortage of DMA buffers for SCSI. 18Gb files are bad bad bad. tmpwatch should delete them. ;o)
Wow, I've been reassigned my own bug report. Fun. ;o)
And finally I've gotten around to fixing it too. ;o) Added the following to CFLAGS -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 Will appear in rawhide tmpwatch 2.8.3