Bug 457271 - condor_config.local sets up LOCK in /tmp
condor_config.local sets up LOCK in /tmp
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: grid-maint-list
Kim van der Riet
Depends On: 449043
  Show dependency treegraph
Reported: 2008-07-30 12:05 EDT by Matthew Farrellee
Modified: 2008-08-11 13:55 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-08-11 13:55:40 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Matthew Farrellee 2008-07-30 12:05:07 EDT
+++ This bug was initially created as a clone of Bug #449043 +++

that's bad policy as /tmp can be cleaned. would be better to have it in

-- Additional comment from mfarrellee@redhat.com on 2008-06-05 09:43 EST --
condor_config also puts C_GAHP_LOCK in /tmp

-- Additional comment from mfarrellee@redhat.com on 2008-07-23 13:59 EST --
Underlying issue is concern that tmpwatch will delete locks, this is addressed
in 7.0.4 by LOCK_FILE_UPDATE_INTERVAL (defaults to 8 hours)

Available in 7.0.4-1
Comment 3 errata-xmlrpc 2008-08-11 13:55:40 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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