Bug 457271

Summary:	condor_config.local sets up LOCK in /tmp
Product:	Red Hat Enterprise MRG	Reporter:	Matthew Farrellee <matt>
Component:	grid	Assignee:	grid-maint-list <grid-maint-list>
Status:	CLOSED ERRATA	QA Contact:	Kim van der Riet <kim.vdriet>
Severity:	low	Docs Contact:
Priority:	low
Version:	1.0	CC:	jneedle
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:	2008-08-11 17:55:40 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:
Bug Depends On:	449043
Bug Blocks:

Description Matthew Farrellee 2008-07-30 16:05:07 UTC

+++ 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
/var/lib/condor

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

-- Additional comment from mfarrellee 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 17:55:40 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-0816.html