Bug 8987
Summary: | tmpwatch deletes file while in use | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Simon Hill <simon> |
Component: | tmpwatch | Assignee: | Preston Brown <pbrown> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 6.0 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2000-02-14 19:20:17 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Simon Hill
2000-01-30 17:16:33 UTC
Change the tmpwatch policy (probably by disabling) if you're going to put unusual things in /tmp. There's no (easy) way that tmpwatch can discover that a file is in use. I have to respectfully disagree with this. While in this instance, I was making an unusual use of /tmp, there are a number problems with not checking whether the file is open before deleting it. As more and more commercial software is developed for Linux, /tmp may be used in ways not expected. Even free software may use /tmp in ways you don't expect. For example, Meta-HTML (www.metahtml.org) is a web-server which puts its session database in /tmp by default. Of course, once tmpwatch deletes it, it continues to work ... but none of the other utilities designed to access the session database will work. While it may in INCONVENIENT to fix this, I doubt that it is difficult - the code is in lsof. we have added a flag to use fuser to determine whether a file is open or not for 6.2. However, this option is turned off by default. |