[LWN Logo]

Date: Mon, 06 Sep 1999 14:30:50 -0600
From: Alan Robertson <alanr@bell-labs.com>
To: Linux-HA mailing list <linux-ha@muc.de>
Subject: Comments wanted: heartbeat and the FHS

It has been brought to my attention that heartbeat isn't very close to
conforming to the Linux Filesystem Hierarchy Standard.  I looked at the standard
in more detail, and this is surely the case.

You can find the FHS documents here:
	http://www.pathname.com/fhs/

I have been unable to reach the LSB (Linux Standards Base) web server for the
last couple of days, so I've gone on without them :-)

As it is now, most things are under /etc.  I suppose this is probably due to
equal parts of laziness and expedience  :-)

I am in the process of deciding where to move things to conform to the FHS, and
have come to the conclusions listed below.  Please comment on these conventions,
and let me know if you disagree, or have another interpretation of the FHS than
mine.

The proposed new hierarchy is described below:

Under /etc/ha.d:
	/etc/ha.d/ha.cf and /etc/ha.d/ipresources and the new key file
		Configuration files
	From the FHS:
		"/etc contains configuration files and directories that are
                specific to the current system."

	The scripts in /etc/ha.d/init.d, rc.d, and resource.d are analagous by
	design to the scripts in /etc/rc.d/init.d, and can be system-specific.

Under /usr/lib/heartbeat:
	The current /etc/ha.d/bin  From the FHS:
	"/usr/lib includes object files, libraries, and internal binaries
	that are not intended to be executed directly by users or
	shell scripts."

Under /var/run:
	/var/run/ppp.d		(info on running PPP processes)
	/var/run/heartbeat-fifo	By analogy to this statement in the FHS:
		"Programs that maintain transient UNIX-domain sockets should
        	place them in this directory". [/var/run]

	Thanks in advance!

	-- Alan Robertson
	   alanr@bell-labs.com

------------------------------------------------------------------------------
Linux HA Web Site:
  http://www.henge.com/~alanr/ha/
Linux HA HOWTO:
  http://metalab.unc.edu/pub/Linux/ALPHA/linux-ha/High-Availability-HOWTO.html
------------------------------------------------------------------------------