Bug 16217 - default state file location is a VERY BAD choice
Summary: default state file location is a VERY BAD choice
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pvm   
(Show other bugs)
Version: 7.0
Hardware: All Linux
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact:
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2000-08-15 04:32 UTC by Alexander L. Belikoff
Modified: 2008-05-01 15:37 UTC (History)
1 user (show)

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

Attachments (Terms of Use)

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

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