Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 16217

Summary: default state file location is a VERY BAD choice
Product: [Retired] Red Hat Linux Reporter: Alexander L. Belikoff <abel>
Component: pvmAssignee: Trond Eivind Glomsrxd <teg>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: high    
Version: 7.0CC: alan
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-08-15 19:18:10 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:

Description Alexander L. Belikoff 2000-08-15 04:32:54 UTC 
When started, pvmd3 creates a couple of files keeping its state:
pvm[dl].<UID> . By default, it puts them into /tmp.

The problem is, PVM daemon doesn't touch those files after that. Thus, in
case there is no PVM activity for 10 days or such, the state files will get
removed by tmpwatch. This renders PVM majorly messed up, when only
kill(1)ing a daemon and restarting it can help.

The proper solution is:

a. In %postinstall script:

mkdir -p /var/run/pvm
chmod 1777 /var/run/pvm


b. In /etc/init.d/pvm:

export PVM_TMP=/var/run/pvm
Comment 1 Trond Eivind Glomsrxd 2000-08-15 13:45:23 UTC 
Agreed - some programs can run for a long time (and for a little used cluster,
there doesn't need to be anything running for that period of time). Will fix.
Comment 2 Alan Cox 2000-08-15 19:00:40 UTC 
That isnt all you can do....
Comment 3 Trond Eivind Glomsrxd 2000-08-15 19:04:00 UTC 
Aha? I have a fixed RPM, but what could you do?
Comment 4 Trond Eivind Glomsrxd 2000-08-15 19:18:08 UTC 
Submitted to the tree