Bug 12771 - tmpwatch should not be enabled by default
Summary: tmpwatch should not be enabled by default
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: tmpwatch
Version: 6.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Preston Brown
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-06-21 02:56 UTC by Fyodor
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-06-21 02:56:15 UTC
Embargoed:


Attachments (Terms of Use)

Description Fyodor 2000-06-21 02:56:14 UTC
By default, Redhat 6.2 seems to install tmpwatch in cron.daily, set to
delete any files that haven't changed in 10 days.  The installation did not
warn me about this, and I ended up losing many important files.  I think
Redhat should ask the user before putting such a destructive command into
cron.  Why not disable it by default and let the user add it if they really
want this functionality?  It is better to default to "safe" operation in my
humble opinion.  The risk of having it disabled by default (unwanted files
piling up) seems far less severe than the risk of default-enabled
(important files deleted before they can be filed out of /tmp ).

Yes, I realize /tmp isn't the best place for important files, but IMHO that
does not mean you should arbitrarily decide that they should be deleted
every 10 days without informing the user.

Comment 1 Preston Brown 2000-09-11 18:46:48 UTC
we have done this since Red Hat Linux 2.x.  I will inform the docs team that
this needs to be addressed in the documentation.

However, we will continue to ship with tmpwatch on.  /tmp is _not_ a good place
to store _anything_.


Note You need to log in before you can comment on or make changes to this bug.