Bug 1330328

Summary: tmpwatch doesn't support --fuser
Product: Red Hat Enterprise Linux 7 Reporter: Davide Cavalca <davide>
Component: tmpwatchAssignee: Jiri Kucera <jkucera>
Status: CLOSED ERRATA QA Contact: David Jež <djez>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.1CC: afox, djez, jkucera, ovasik
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: tmpwatch-2.11-6.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-06 12:58:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1630904, 1630910, 1630919, 1660473    
Attachments:
Description Flags
Diff of updated tmpwatch.spec none

Description Davide Cavalca 2016-04-25 22:25:20 UTC 
Description of problem: It looks like the tmpwatch package was built without fuser support. This is a regression from CentOS 6.



Version-Release number of selected component (if applicable): 2.11-5.el7


How reproducible: always


Steps to Reproduce:
1. tmpwatch --fuser 

Actual results:
it just prints the help message, where the --fuser option is missing

Expected results:
it should do something useful

Additional info:
We noticed that when building tmpwatch in mock, the fuser test in configure will always fail, as /proc is not mounted in the chroot. We worked around this internally by stubbing out the test and rebuilding the package.
Comment 2 Jiri Kulda 2016-08-30 14:52:46 UTC 
Created attachment 1195952 [details]
Diff of updated tmpwatch.spec
Comment 3 Jiri Kulda 2016-08-30 15:12:46 UTC 
Hi,
I created a patch for this bug. After I receive all needed acks I'll push it into upstream. Thanks for letting me know about this problem. 
If you will have any future problems please use customer portal because bugzilla is not a support tool.
Thanks for understanding.
Jiri
Comment 13 errata-xmlrpc 2019-08-06 12:58:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2147