FAXSTAT(1)
β¨ FAXSTAT(1) β display HylaFAX status β¨
okay bestie, welcome to the General Commands Manual page for FAXSTAT(1) β aka faxstat. This is part 1, and it's giving Unix-but-make-it-cute. π
π NAME π
faxstat β display HylaFAX status
π SYNOPSIS π
faxstat [ -O config ] [ options ]
πΈ DESCRIPTION πΈ
faxstat reports the status of HylaFAX servers, including (potentially) the status of the send, receive, done, document, and archive directories. When invoked without options faxstat reports only the status of the server; the options described below can be used to override this behavior.
Server status information indicates the state of the server (idle, sending, receiving, etc.) and the phone number that is associated with the fax modem.
The job queue report gives the status of facsimile jobs queued for transmission; by default:
- the job identifier,
- the job state (see below for the description of a format in the
JobFmtstring), - the modem or modem class the job is bound to (
anyif the job can be sent through any modem), - the destination (phone number) of the job,
- the time to send the job, or a blank field if the job is being processed or is to be sent immediately,
- the job's owner,
- and status information about the job (typically the reason why a previous attempt failed).
The receive queue report lists the facsimile documents that have been received and are awaiting delivery; by default it includes:
- the document protection mode,
- the number of pages,
- the document's owner,
- the phone number of the sender (if supplied),
- the date and time at which the job was received, and
- the filename of the document in the
recvqdirectory on the server machine.
β¨ OPTIONS β¨
-Aβ Login with administrative privileges.-aβ Display the contents of the archive directory on the server machine.-dβ Display the status of all jobs that have completed; i.e. those jobs located in thedoneqdirectory on the server machine. TheJobFmtstring defines the content and format of information reported with this option.-fβ Display the status of document files located in thedocqdirectory on the server machine. TheFileFmtstring defines the content and format of information reported with this option (see below).-gβ Display times and dates in Greenwich Mean Time (GMT). NB: this is the default.-h hostβ Report the status of the server on a specific host. The host may be either a symbolic name or a network address. IPv6 addresses are given in[xx:xx::x]:portformat. If no-hoption is supplied,faxstatuses theFAXSERVERenvironment variable to identify the HylaFAX server to contact. If this variable is not set, thenfaxstatchecks for a setting in the configuration files (first in the per-user file and then in the system-wide file). If all of the above fails, thenfaxstatattempts to contact a server on the machine where it is run.-iβ Display additional status information for the server as given by/var/spool/hylafax/status/any.info. This status typically has information such as the HylaFAX version, the physical location of the server machine, and an administrative contact for the server. Seestatus(5F).-lβ Display times and dates in the local timezone of the server.-nβ Suppress the display of server and modem status.-o loginβ Specify the fax owner login name. If unspecified, the user's current login name is used. The login password and admin password may also be provided by separating them from the owner login name with colons, likeowner:pass:adminpass.-qβ Display the sequence numbers of the HylaFAX queues.-rβ Display the receive queue status for each server. TheRcvFmtstring defines the content and format of information reported with this option (see below).-O configβ Treatconfigas a configuration parameter specification that is interpreted after reading the configuration file. For example,-O Host:fax.example.comwould set theHostconfiguration parameter tofax.example.com, overriding any setting in the configuration file.-sβ Display the status of jobs in the send queue on the server machine. TheJobFmtstring defines the content and format of information reported with this option (see below).-vβ Trace the protocol exchanges betweenfaxstatand thehfaxdprocesses on the standard output.
π οΈ CONFIGURATION PARAMETERS π οΈ
faxstat reads configuration information from the file /etc/hylafax/hyla.conf and then from the file ~/.hylarc. Configuration files follow the conventions described in hylafax-client(1). The following configuration parameters are recognized:
FileFmtβ type:string; default:see below; description: format string for file status resultsHostβ type:string; default:localhost; description: host to contact for serviceJobFmtβ type:string; default:see below; description: format string for job status resultsModemFmtβ type:string; default:see below; description: format string for modem status resultsPassiveModeβ type:boolean; default:false; description: whether or not to use passive modePortβ type:integer; default:4559; description: port to use in contacting serverProtocolβ type:string; default:tcp; description: protocol to use in contacting serverRcvFmtβ type:string; default:see below; description: format string for received facsimile status resultsTimeoutβ type:integer; default:3600; description: timeout in seconds waiting for server responseTimeZoneβ type:string; default:GMT; description: timezone to use for reporting dates and timesVerboseβ type:boolean; default:No; description: whether or not to enable protocol tracing
The configuration parameters are explained below:
π FileFmt π
The format string to use when returning file status information with the -f option. Formats are specified using printf(3S)-style conventions but using the field identifiers listed below. Each item can include field width, precision, left-justification, 0-filling, etc. just as for printf; e.g. %-8p for an 8-character wide, left-justified, blank-padded field containing the file protection flags.
aβ Last access timecβ Creation timedβ Device number (octal)fβ Filenamegβ Group identifier (decimal)iβ Inode number (decimal)lβ Link count (decimal)mβ Last modification timeoβ Owner (based on file GID)pβ Fax-style protection flags (no group bits)qβ UNIX-style protection flagsrβ Root device number (octal)sβ File size in bytes (decimal)uβ User identifier (decimal)
π Host π
The host to contact for service. (Equivalent to the -h option.)
π JobFmt π
The format string to use when returning job status information for the -s and -d options. Formats are specified using printf(3S)-style conventions but using the field identifiers listed below. Each item can include field width, precision, left-justification, 0-filling, etc. just as for printf; e.g. %-3j for a 3-character wide, left-justified, blank-padded field containing the job state.
Aβ Destination SubAddressBβ Destination PasswordCβ Destination company nameDβ Total # dials/maximum # dialsEβ Desired signalling rateFβ Client-specific tagline format stringGβ Desired min-scanline timeHβ Desired data formatIβ Client-specified scheduling priorityJβ Client-specified job tag stringKβ Desired use of ECM (one-character symbol)Lβ Destination geographic locationMβ Notification e-mail addressNβ Desired use of private tagline (one-character symbol)Oβ Whether to use continuation cover page (one-character symbol)Pβ # pages transmitted/total # pages to transmitQβ Client-specified minimum acceptable signalling rateRβ Destination person (receiver)Sβ Sender's identityTβ Total # tries/maximum # triesUβ Page chopping threshold (inches)Vβ Job done operationWβ Communication identifierXβ Job type (one-character symbol)Yβ Scheduled date and timeZβ Scheduled time in seconds since the UNIX epochaβ Job state (one-character symbol)bβ # consecutive failed triescβ Client machine namedβ Total # dialseβ Public (external) format of dialstringfβ # consecutive failed dialsgβ Group identifierhβ Page chop handling (one-character symbol)iβ Current scheduling priorityjβ Job identifierkβ Job kill timelβ Page length in mmmβ Assigned modemnβ E-mail notification handling (one-character symbol)oβ Job ownerpβ # pages transmittedqβ Job retry time (MM::SS)rβ Document resolution in lines/inchsβ Job status information from last failuretβ Total # tries attempteduβ Maximum # triesvβ Client-specified dialstringwβ Page width in mmxβ Maximum # dialsyβ Total # pages to transmitzβ Time to send job
okay so the format letters just keep going, bestie, we're still in the format-string zone and there is no escape π
Kβ spits outD'' when ECM is getting disabled, a plain'' (space) when ECM use is enabled,H'' when T.30 Annex C half duplex is on, andF'' when T.30 Annex C full duplex is on.Nβ gives you'' (a space) if the system-wide tagline format is the one being used, orP'' if a private tagline format is in play.OβN'' means no continuation cover page,'' (space) means just use the system default handling for continuation cover pages.XβF'' for a facsimile job,P'' for a pager job. cute lil discriminator β¨aβ the whole mood ring of job states, fr fr:- ``?'' β job is in an undefined state
- ``T'' β suspended job (not being scheduled)
- ``P'' β pending job (waiting for its time to send to arrive)
- ``S'' β sleeping job (waiting for a scheduled timeout, like a delay between attempts to send)
- ``B'' β blocked by concurrent activity to the same destination
- ``W'' β waiting for resources, like a free modem
- ``R'' β actively running, main character energy
- ``D'' β done, and it was a success π
- ``F'' β failed to complete π
hβD'' if page chopping is disabled,'' (space) for the system default page chop handling,A'' when all pages are to be chopped,L'' if only the last page gets chopped.nβ'' (space) when no notification messages are to be delivered,D'' when notification is sent when the job is done,Q'' when notification is sent each time the job is requeued,A'' when notification goes out for either the job completing or being requeued.
ngl, it is recommended that all items include a field width, so the width of column title strings can be constrained when you're constructing headers from the format string. do with that what you will π«Ά
β¨ CONFIGURATION PARAMETERS (continued) β¨
ModemFmtβ the format string to use when returning modem status information. Formats useprintf(3S)-style conventions but with the field identifiers below. Each item can include field width, precision, left-justification, 0-filling, etc., just likeprintfβ e.g.%-8hfor an 8-character wide, left-justified, blank-padded field containing the name of the host the server is running on. iconic.hβ server hostnamelβ local identifier stringmβ canonical modem namenβ FAX phone numberrβ maximum pages that can be received in a single callsβ status information stringtβ server and session tracing levels (xxxxx:yyyyy)vβ modem speaker volume as a one-character symbolzβ a*'' if a `faxgetty(8C)` process is running; otherwise'' (a space)
PassiveModeβ whether or not to use passive mode when talking to the server.Portβ the network port to contact for service. (Equivalent to the-hoption.)Protocolβ the name of the communication protocol to use when contacting a server. (Equivalent to theFAXSERVICEenvironment variable.)RcvFmtβ the format string to use when returning status information for the-roption. Formats useprintf(3S)-style conventions but with the field identifiers below. Each item can include field width, precision, left-justification, 0-filling, etc., just likeprintfβ e.g.%-3bfor a 3-character wide, left-justified, blank-padded field containing the signalling rate. obsessed πYβ extended representation of the time when the receive happenedaβ SubAddress received from sender (if any)bβ signalling rate used during receivedβ data format used during receiveeβ error description if an error occurred during receivefβ document filename (relative to therecvqdirectory)hβ time spent receiving document (HH:MM:SS)iβ CIDName value for received faxjβ CIDNumber value for received faxlβ page length in mmmβ fax-style protection mode string (``-rwxrwx'')nβ file size (number of bytes)oβ file ownerpβ number of pages in documentqβ UNIX-style protection flagsrβ resolution of received datasβ sender identity (TSI)tβ compact representation of the time when the receive happenedwβ page width in mmzβ a*'' if receive is going on; otherwise'' (a space)
and yes, same energy as before: it is recommended that all items include a field width so that the width of column title strings can be constrained when constructing headers from the format string.
TimeZoneβ controls whether times and dates get reported in the local timezone of the server (local'') or in GMT (gmt''). By default, times are reported in GMT. βTimeoutβ the timeout, in seconds, to wait for a server response.Verboseβ control protocol tracing. (Equivalent to the-voption.)
πΈ NOTES πΈ
The server login user name may be specified by the FAXUSER environment variable. iykyk π§
π BUGS π
There is no way to suppress the server status report. There is no way to control the printing of headers. that's just how it is, bestie, we don't make the rules π
π FILES π
/etc/hylafax/hyla.confβ system-wide configuration file~/.hylarcβ per-user configuration file
π SEE ALSO π
hylafax-client(1), sendfax(1), faxalter(1), faxrm(1), hfaxd(8C)
and that's the whole page, periodt. this lil legend is FAXSTAT(1), dated July 9, 1996 β vintage but she ate, fr fr. slay, go fax something πβ¨π¦
π¦ where this page comes from
- fedora 43: hylafax+-client 7.0.11-4.fc43 Β· libtiff AND LicenseRef-Callaway-BSD-with-advertising
- fedora 43: hylafax+-client 7.0.11-4.fc43 Β· libtiff AND LicenseRef-Callaway-BSD-with-advertising
- fedora 44: hylafax+-client 7.0.11-5.fc44 Β· libtiff AND LicenseRef-Callaway-BSD-with-advertising
- fedora 44: hylafax+-client 7.0.11-5.fc44 Β· libtiff AND LicenseRef-Callaway-BSD-with-advertising
- opensuse-leap 16.0: hylafax+-client 7.0.10-bp160.1.20 Β· BSD-3-Clause
- opensuse-leap 16.0: hylafax+-client 7.0.10-bp160.1.20 Β· BSD-3-Clause
- opensuse-leap 16.0: hylafax+-client 7.0.10-bp160.1.20 Β· BSD-3-Clause
- opensuse-leap 16.0: hylafax+-client 7.0.10-bp160.1.20 Β· BSD-3-Clause
- 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