Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 54443
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Aaron Walker (RETIRED) <ka0ttic@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Janne Pikkarainen <jaba@mikrobitti.fi>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 54443 depends on: Show dependency tree
Bug 54443 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-06-19 11:46 0000 
It would be nice if tmpwatch ebuild could include a reasonable cron entry for
it. Anyway, tmpwatch is by nature a cron-driven program, so putting something
like this (shamelessly ripped from Red Hat) to /etc/cron.daily/tmpwatch or so
would be cool:

---
/usr/sbin/tmpwatch 240 /tmp
/usr/sbin/tmpwatch 720 /var/tmp
for d in /var/{cache/man,catman}/{cat?,X11R6/cat?,local/cat?}; do
    if [ -d "$d" ]; then
        /usr/sbin/tmpwatch -f 720 $d
    fi
done
---

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

------- Comment #1 From Aaron Walker (RETIRED) 2004-09-18 09:43:16 0000 ------- 
As I see this package is fair game (owned by bug-wranglers), I'll be
maintaining it (and taking its open bugs).

------- Comment #2 From Aaron Walker (RETIRED) 2004-09-18 12:52:09 0000 ------- 
Just bumped tmpwatch to 2.9.1-1, which includes a cron script (disabled by
default) installed into /etc/cron.daily.  Includes examples for some common
uses such as deleting old distfiles.  Thanks for the report.

------- Comment #3 From Aaron Walker (RETIRED) 2004-09-18 12:53:36 0000 ------- 
Forgot to mention, if for some reason you notice anything wrong with the cron
script, please repoen this bug, instead of filing a new one.  Thanks again.

------- Comment #4 From Janne Pikkarainen 2004-09-19 05:14:37 0000 ------- 
Looks good. Thank you and keep up the good work!

------- Comment #5 From ra 2004-09-19 18:33:32 0000 ------- 
Noticed a typo:

#PORTAGE_TMPDIR="$(portageq envvar PORTAGE_TMP_DIR)/portage"

should be

#PORTAGE_TMPDIR="$(portageq envvar PORTAGE_TMPDIR)/portage"

------- Comment #6 From Aaron Walker (RETIRED) 2004-09-20 02:21:54 0000 ------- 
Fixed.  Thanks very much for pointing that out.

------- Comment #7 From Lionel Bouton 2005-05-08 04:16:34 0000 ------- 
The cron script gives the following example:

# Delete everything in PORTAGE_TMPDIR that hasn't been modified in 2 weeks.
#
#if [[ -d ${PORTAGE_TMPDIR:-/var/tmp/portage} ]]; then
#  ${TMPWATCH} --mtime --all 336 ${PORTAGE_TMPDIR:-/var/tmp/portage}
#fi

It bited me when I activated this one because the mtime of the source files unpacked in /var/tmp/portage can be earlier than what tmpwatch expects.
An emerge running while this command is run can fail or leave the system in an unknown state.

--mtime should be changed in --atime and the user advised to check that /var/tmp/portage isn't on a filesystem mounted with 'noatime'.

------- Comment #8 From Aaron Walker (RETIRED) 2005-05-08 04:53:26 0000 ------- 
Please open a seperate bug.  A patch for this would be greatly appreciated.
Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug