Re: FHS, macros, and Pinstripe

[Jeff Johnson <jbj JBJ ORG>]

On Thu, Aug 31, 2000 at 05:11:14PM -0700, Kenneth Porter wrote:
> As a packager of a few daemons, I'm concerned about what I need to do
> to my spec files to prepare for Pinstripe and FHS compliance. For
> example, I package qpopper, which installs an inetd-launched POP3
> daemon. Currently it goes in /sbin along with other in.* binaries.
> Where would it go in Pinstripe? (I'm guessing /usr/sbin.) Are there
> macros I can use to place it in the correct directory for old and new
> distributions?
> 

/usr/sbin is almost certainly the place for an inetd-launched daemon,
and that location hasn't changed in Pinstripe. There is %_sbindir if
you wish to use a macro for the file path.

A harder issue will be xinetd vs. inetd. If just inetd, you would
use %post/%preun to add/delete entries to /etc/inetd.conf. If just
xinetd, you could simply add appropriate /etc/xinetd.d/foo to %files.
If you wish you package to install on both, you will need to, for example,
check for /etc/xinetd.d to detect an xinetd system and then create the
xinetd entry directly.

There's also the issue of restarting inetd/xinetd to activate your service.
IIRC (verify by checking some daemon package(s)) Pinstripe tries to execute
/etc/init.d/xinetd condrestart. Previous versions of Red Hat left it
to a reboot/sysadmin to restart inetd (that's probably OL for you too.)

73 de Jeff

-- 
Jeff Johnson	ARS N3NPQ
jbj@jbj.org	(jbj@redhat.com)
Chapel Hill, NC