Bug 449043 - condor_config.local sets up LOCK in /tmp
Summary: condor_config.local sets up LOCK in /tmp
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: grid
Version: beta
Hardware: All
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Matthew Farrellee
QA Contact: Kim van der Riet
URL:
Whiteboard:
Depends On:
Blocks: 457271
TreeView+ depends on / blocked
 
Reported: 2008-05-30 00:11 UTC by Matthew Farrellee
Modified: 2008-08-11 17:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-11 17:48:27 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2008:0814 0 normal SHIPPED_LIVE Moderate: condor security and bug fix update 2008-08-11 17:48:14 UTC

Description Matthew Farrellee 2008-05-30 00:11:07 UTC
that's bad policy as /tmp can be cleaned. would be better to have it in
/var/lib/condor

Comment 1 Matthew Farrellee 2008-06-05 13:43:35 UTC
condor_config also puts C_GAHP_LOCK in /tmp

Comment 2 Matthew Farrellee 2008-07-23 17:59:28 UTC
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 7 errata-xmlrpc 2008-08-11 17:48:27 UTC
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.

http://rhn.redhat.com/errata/RHSA-2008-0814.html


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