Bug 16217 - default state file location is a VERY BAD choice
default state file location is a VERY BAD choice
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: pvm (Show other bugs)
7.0
All Linux
high Severity medium
: ---
: ---
Assigned To: Trond Eivind Glomsrxd
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-08-15 00:32 EDT by Alexander L. Belikoff
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-08-15 15:18:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Alexander L. Belikoff 2000-08-15 00:32:54 EDT
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 09:45:23 EDT
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 15:00:40 EDT
That isnt all you can do....
Comment 3 Trond Eivind Glomsrxd 2000-08-15 15:04:00 EDT
Aha? I have a fixed RPM, but what could you do?
Comment 4 Trond Eivind Glomsrxd 2000-08-15 15:18:08 EDT
Submitted to the tree

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