INSTALLATION of DAEMONTOOLSX
============================

Requirements
------------

1.  daemontoolsx uses the slashpackage format
    for installation (see below) and the directory
    - /package (chmod 644) shall exist.
2.  daemontoolsx requires the fehQlibs (>= 31)
    to be successfully compiled and linked.

Configuration
-------------

3.  fehQlibs need to be installed and 
    libqlibs.a together with the header files
    are available.
    The most common place is to install the
    fehQlibs at /usr/local and symlink them
    to qlibs:  ln -s fehQlibs-XY qlibs
    This is the default location in in conf-qlibs.
5.  The configuration files
    - conf-cc (compiler options)
    - conf-ld (loader options)
    are usually untouched.
6.  The location of the man-pages are evaluated
    automatically. If not, use
    - conf-man 
    to cope with your local settings.
7.  The standard location of the generated 
    daemontoolsx modules is
    - /command 
    as provided in
    - conf-home
    This is matter of adjustments.
8.  Use 
    - ./package/command-cp and
    - ./package/command-ln (default: /usr/local/bin)
    to copy or symlink those to other locations,
    if required.
9.  Services are exepected as given in
    - conf-service 
    by default /service to be provissioned to
    svscanboot (only). You can change this.

Installation
------------

10. The tar-archive has to be extracted in
    - /package.
11. The modules will be installed with their
    current version at
    - /package/admin/daemontoolsx/daemontoolsx-X.YZ.
12. Change to that directory, apply the required
    modifications as discussed above and call
    - package/install.
13. A step-by-step installation is also possible:
    - package/compile => modules will be compiled
      and linked; available under ./command.
14. You may want to test the resulting modules calling 
    - package/rts.
15. Man-pages are raised and installed by means of 
    - package/man.
    respecting nroff and mandoc formats.
16. A potential upgrade is provided by 
    - package/upgrade.
17. The final setup is provided calling
    - package/run.
18. Now, supervise will be called on start of your
    OS potentially using the rc.local mechanism or
    the inittab.
19. If you prefer supervise to be called by systemd
    and thus all depended services share the same
    c-group use the unit file avalable at
    - systemd
    to be included on startup here.
20. If you like to report success, call
    - package/report.

Integration at start
--------------------

There are several ways to invoke svscanboot during
startup of your system:

Automatically (by package/run):

21. System V: Extension to /etc/inittab
22. *BSD: Extension to /etc/rc.local

Manually:

23. For Systemd based systems use from this package:
     - systemd/daemontools.service 
    as template for a working unit file.
    
24. By modifying the service path in svscanboot 
    and providing appropriate script names, 
    serveral distinct service directories can be 
    tasked and supervised.
    
    
feh, April 2026.