Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Description of problem: tmpwatch have no option to prevent crossing filesystem bounds. How reproducible: Every time Steps to Reproduce: 1. BACKUP=`mktemp -d` 2. mount -o bind / $BACKUP 3. mount -o bind /boot $BACKUP/boot ... n. run long backup job on $BACKUP Actual results: tmpwatch cron start and delete many usefull stuff in $BACKUP. Expected results: tmpwatch should not enter other filesystems mounted in /tmp.
Thanks for your report. No additional option is needed, because tmpwatch never traverses to a different filesystem already by default. The problem you have encountered happened because a bind mount is not treated as a "different filesystem" in the RHEL 5 and RHEL 6 versions of tmpwatch. If you are a Red Hat customer with an active subscription, please report the problem using the Red Hat Customer Portal at http://access.redhat.com/ for correct prioritization of the issue.
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux.
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).