Under a System V-based operating system the normal installation procedure sets up the system so the faxq and hfaxd processes are started up by init(1M). On other systems you will need to arrange for this yourself (typically by editing /etc/rc.local or similar). faxgetty processes must be manually setup by editing the appropriate control file for init; usually either /etc/inittab or /etc/ttytab. hfaxd can be setup to be started by inetd when the faxsetup script is run to configure a system for use with HylaFAX.
If you need to start the faxq server by hand, consult the faxq(1M) manual page and the shell script etc/hylafax that is used on System V-based systems.
Incoming facsimile are placed in the recvq subdirectory of the spooling area and probably will need to be cleaned up periodically. Likewise there is logging information in the log subdirectory and accounting information in the etc subdirectory of the spooling area that may need some attention.
The faxcron script is designed to handle the periodic maintenance of the spooling area. This script is designed to be run from cron(1) every day.
If you want to do accounting check out the xferstats and recvstats scripts for a basic attack on how to process the etc/xferlog accounting file that has records of all facsimile transmissions and receptions. Note that faxcron uses these scripts to deliver statistics about facsimile that were recently transmitted and received.
Otherwise the only matter to be concerned with is the support for data connections. If your modems are capable of differentiating data connections from facsimile connections the fax server can be configured to startup a getty program whenever a call from a data modem is received. Alternatively, if your modem does not support an adaptive-answer facility, but it is a Class 1 modem, the server may be able to do adaptive answering in software. In any event, beware that if you enable data connections you should take the normal precautions you would take when there are dialup ports on your machine. Specifically, make sure that you have passwords, appropriate file protections, and proper configuration of uucp or similar.
If you encounter problems sending or receiving facsimile you can
enable copious tracing information by editing the HylaFAX
Consult the Troubleshooting
section and the
hylafax-config(4F) manual page,
in particular, for help.
There is also information in the
HylaFAQ on problems one might encounter during
Controlling Modem Usage
HylaFAX provides a great of flexibility in how modems on a server
machine are used.
Modems can be constrained for outbound-only use, inbound-only use, or both.
Modem priorities (see the section in the
``Advanced Server Setup'' chapter)
can be used to control the order in which modems are assigned to outbound
Modems can also be dynamically taken off-line for either inbound or
outbound use by using the faxstate or faxconfig commands.
For example, to mark a modem as ``busy'' or ``down'' so that it is not
assigned to an outbound job the faxstate command would be used:
hyla# faxstate -s busy ttyf2
hyla# faxconfig -m ttyf2 RingsBeforeAnswer 0
|HylaFAX documentation.||HylaFAX table of contents.|