FAXSEND(8)
π FAXSEND(8) β the faxsend girlies' guide π
System Manager's Manual β¨ FAXSEND β¨
okay bestie, sit down, we're talking about faxsend, the HylaFAX facsimile transmit program. she's the one doing the actual faxing. π
πΈ NAME πΈ
faxsend β HylaFAX facsimile transmit program π«Ά
β¨ SYNOPSIS β¨
/usr/sbin/faxsend [ -l ] [ -p ] [ -c config ] -m device-ID qfile [qfile
[qfile [...]]]
π DESCRIPTION π
so faxsend is literally the program that implements the facsimile transmission protocol for the HylaFAX system. she's the main character of actually sending the fax. π
she gets invoked by the faxq scheduler process, once for every single facsimile transmit attempt. and she comes in with assumptions, okay, so let's vibe check them:
- her current working directory is the top of the spooling hierarchy π
- a suitable modem device has already been allocated for her use π
- all the documents to be sent are already converted to TIFF/F (TIFF Class F), at the appropriate resolution and with an appropriate data encoding β¨
and in normal use faxsend will inherit a lockfile for the modem from the faxq process. no cap. π
the format of the job description file you pass on the command line is described over in sendq(5) β go read her, iykyk. π
then faxsend initializes the modem before attempting to transmit the facsimile, using the info in the appropriate modem configuration file. and here's the thing β if the modem does not respond to this initialization, faxsend will repeatedly try to initialize the modem. this behaviour is required for send-only environments where a faxgetty(8) process is not run (and the modem would be known to be in a properly initialized state). she's persistent, she's not giving up, periodt. πͺ
faxsend catches SIGINT and SIGTERM and cleans up any resources she controls β and this is literally the mechanism faxq uses to abort a job while it's in progress. so if a job gets cancelled, that's her tidying up on her way out. π§Ή
batching π β multiple fax jobs of documents with varying formatting may be sent in one fax call by "batching" them, which you do by supplying faxsend with multiple qfile entries. multiple files, one call, efficient queen. π₯
and many aspects of faxsend operation are controlled through a configuration file π β it lives in the spooler hierarchy in the etc subdirectory and is named config.device-ID. for detailed info on what goes in there, consult hylafax-config(5). she's got lore. β¨
π OPTIONS π
the following options are recognized:
-cconfig β treat config as a configuration parameter specification that gets interpreted after reading the per-device configuration file. for example,-c sessiontracing:0x4fwould set theSessionTracingconfiguration parameter to0x4f, overriding any setting in the configuration file. overrides? she said yes. π-mdevID β the device to use in processing the job. β οΈ note that this is a device identifier and not the pathname of the tty special file. a device identifier is formed from a device filename by removing any leading/dev/and converting any/characters to_characters. so yes bestie, that transformation is real and you have to do it. π-lβ do the UUCP lockfile protocol infaxsenditself. by defaultfaxsendassumes she's invoked with the device already locked and that she does not need to manage the lockfile. so-lis her taking the lockfile duties onto herself. π-pβ do not change the process priority when transmitting. normallyfaxsendwill raise her priority to reduce i/o latency β so this option is useful for debugging. π
π¦ NOTES π¦
faxsend returns the new job status to faxq through the returned value in the associated qfile. the possible values, bestie:
send_retryβ retry job πsend_failedβ job finished without success πsend_doneβ job completed successfully βsend_reformatβ job should be retried after documents are reformatted π
π FILES π
/var/spool/hylafax/etc/config.devIDβ device-specific configuration file π
consult hylafax-server(5) for a complete discussion of the structure and content of the spooling area. she has the whole map of the spooling area, fr fr. πΊοΈ
β SEE ALSO β
faxq(8), hylafax-server(5), hylafax-config(5)
and that's the whole page, bestie!! π«Ά this one is from the System Manager's Manual, dated October 3, 1995 β yeah she's an icon from '95 and she still faxes better than everyone. πβ¨ mwah, go send a fax. π
π¦ 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