HylaFAX The world's most advanced open source fax server |
* A J Stiles <hylafax_resp@xxxxxxxxxxxxxxx> [070207 04:59]: > The upshot of all of which is: > > If you compiled your Hylafax from source, and accepted all the defaults, it > will put its configuration files in /var/spool/hylafax/etc/. If you > installed a Hylafax RPM or DEB package from your distributor, then it most > probably will put its configuration files in somewhere like /etc/hylafax/. Just a small clarification: HylaFAX (stock) configuration files are read from 2 places, depending on their purpose: FAX_SPOOLDIR "/" FAX_ETCDIR (defaults to /var/spool/hylafax/etc) This are where the "fax server operations" config files are, specifically: $SPOOL/etc/config faxq config file $SPOOL/etc/config.<devid> faxgetty/faxsend/pagesend device config file and many of the referenced files that faxq/faxgetty/faxsend use, like callid, etc are defaulted to be found in there as well. An admin user actually can edit/manage these files through the FTP like nature of the HylaFAX Client-server protocol and the permision restrictions of hfaxd. FAX_LIBDATA (defaults to /usr/local/lib/fax) This is where "HylaFAX Application" configuration files are stored, like: hfaxd.conf sendfax.conf hyla.conf faxmail.conf sendpage.conf faxcover.ps typerules The strange one in here is hfaxd.conf, which is a "fax server operations" config, but was most likely kept out of the chroot hfaxd operates under as a precaution. The debian packages are slightly more complicated than that because debian's package policy mandates that any config files *must* be stored under /etc/. This means that the debian packages has patches to maintain a "twinning" configs, where it tries to synchronize /etc/hylafax (it's FAX_LIBDATA) with the config files also in $SPOOL/etc. a. -- Aidan Van Dyk aidan@xxxxxxxx Senior Software Developer +1 215 825-8700 x8103 iFAX Solutions, Inc. http://www.ifax.com/
Attachment:
signature.asc
Description: Digital signature