FAXQ(8)
π FAXQ(8) π
okay bestie, welcome to the System Manager's Manual corner of the group chat, section 8, and today's main character is faxq π
β¨ NAME β¨
faxq β the HylaFAX queue manager process π
π¦ SYNOPSIS π¦
/usr/sbin/faxq [ -D ] [ -q queue-dir ]
πΈ DESCRIPTION πΈ
so faxq is literally the central queueing agent for HylaFAX. One (and only one, no cap) faxq process is normally running at all times. She's responsible for scheduling, preparing, and initiating outbound facsimile jobs β and potentially other types of jobs too, she's versatile like that π
faxq can be run by herself to provide outbound-only services, or she can run together with one or more faxgetty(8) processes, in which case inbound services (e.g. receiving facsimile) get provided too. The way that when faxq runs by herself, the set of available modems must be specified using the faxmodem(8) command β yeah that's required, not optional. Every modem specified that way is assumed to exist and to be capable of use as a facsimile modem. But when faxq runs in conjunction with faxgetty processes, you do not need to use faxmodem to specify modems; instead the programs communicate information about the status and capabilities of each modem themselves. That latter setup is the more robust and powerful system and it's the intended way for the software to operate β
faxq receives notification of outbound jobs to process from the hfaxd(8) process, which implements the server-side of the HylaFAX client-server protocol. Notification comes through messages sent to a FIFO special file that faxq listens to. That same file is also used by other administrative programs like faxquit(8) π«Ά
Many aspects of faxq operation may be controlled through a configuration file. This file lives in the spooler hierarchy in the etc subdirectory and is named config (as opposed to the per-modem configuration files named config.devid) β go consult hylafax-config(5) for detailed info on this configuration file. Also note that faxq automatically re-reads her configuration file if it's been changed π It's also possible to dynamically change configuration parameters in a running process with the faxconfig(8) program. But beware, bestie: parameters changed that way will be reset to the values specified in the configuration file if the file gets re-read. So that glow-up is temporary π
β¨ OPTIONS β¨
-q dirβ the specified directory gets treated as the spooling area. The default spooling area,/var/spool/hylafax, is defined at the time the software is built π-Dβ this option forcesfaxqto stay attached to the controlling tty from which she was invoked. In normal operationfaxqwillfork(2)and disassociate herself from the controlling tty. This option is useful for debugging π₯
π FILES π
/var/spool/hylafax/FIFOβ FIFO special file for submitting commands/var/spool/hylafax/etc/configβ configuration file
Consult hylafax-server(5) for a complete discussion of the structure and content of the spooling area π
π SEE ALSO π
faxabort(8), faxconfig(8), faxmodem(8), faxquit(8), faxstate(8), getty(8), hylafax-server(5), hylafax-config(5).
and that's the whole vibe, fr fr β faxq(8) from the System Manager's Manual, dated October 27, 1995 (yes she's an icon from the nineties and she's still slaying π
β¨). mwah, go run your queue bestie π«Άπ
π¦ where this page comes from
- debian bookworm: hylafax-server 3:6.0.7-5
- debian trixie: hylafax-server 3:6.0.7-11.1
- ubuntu jammy: hylafax-server 3:6.0.7-3.1
- ubuntu noble: hylafax-server 3:6.0.7-7
- ubuntu questing: hylafax-server 3:6.0.7-13
- ubuntu resolute: hylafax-server 3:6.0.7-13build1
- ubuntu stonking: hylafax-server 3:6.0.7-13build1
- Copyright (c) 1990-1996 Sam Leffler
- Copyright (c) 1991-1996 Silicon Graphics, Inc
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms