FAXRM(1)
π FAXRM(1) β the "okay so delete that" era β¨
okay bestie, welcome to faxrm(1), from the General Commands Manual era (iykyk). This is your little go-to for yeeting jobs and documents off a HylaFAX server. Let's get into it π
β¨ NAME β¨
faxrm β remove a HylaFAX job or document from a server ποΈπ
πΈ SYNOPSIS πΈ
faxrm [ -a ] [ -d ] [ -p pass[:adminpass] ] [ -u user ] [ -O config ] [ -v ] [ -h hostname ] id...
π¦ DESCRIPTION π¦
okay so. faxrm removes one or more jobs or documents from a HylaFAX server. That's the whole vibe. π
And here's the iconic part: if a job that's about to be removed is currently being processed by a server, it gets aborted first. no half-deletes, no ghost jobs, periodt. β¨
An id is either a number that identifies a job (this is the default behavior, bestie) or β if you pass the -d option β a document pathname. Two completely different flavors of id, so know which one you're in.
Where do you even get these ids, you ask? literally so many places:
- Job identifiers are printed by
sendfax(1)when jobs are queued for transmission. π«Ά - They can also be displayed with
faxstat(1). - The names of documents associated with outbound jobs can be seen by supplying the
-foption tofaxstat. - Documents in the receive queue can be viewed with the
-roption tofaxstat.
Now, the permissions tea π: unprivileged users can only remove jobs or documents that they own. Clients with administrative privileges can remove any job or document β see the -a option below, it's giving main character energy π.
Oh and also, the user name may be specified by the FAXUSER environment variable. π
π OPTIONS π
-aβ Use administrative privileges;faxrmwill prompt for the password to set administrative privileges. π-dβ Interpret eachidas a document pathname. And the cute little detail: if a pathname does not begin with/thenfaxrmautomatically prepends/docq/. π©·-h hostβ Contact the server at the specifiedhost. The host may be either a symbolic name or a network address. IPv6 addresses are given in[xx:xx::x]:portformat. If no server is specified then If no-hoption is supplied,faxrmuses theFAXSERVERenvironment variable to identify the HylaFAX server to contact. If this variable is not set, thenfaxrmchecks 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, thenfaxrmattempts to contact a server on the machine where it is run. it's a whole journey fr fr π-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. iconic override behavior β¨-p pass:adminpassβ The login password and optionally the associated admin password (separated by a colon). If no password is given then the user will be prompted if one is required. If-ais used and no adminpass is given, then the user will be prompted for it. π«Ά-u userβ The login username to use in client-server communication protocol. If no user is given then the user will be prompted if one is required.-vβ Trace the protocol messages to and from the server. ngl this one's for the girlies who love seeing the raw receipts π₯
π CONFIGURATION PARAMETERS π
faxrm 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:
Hostβ Type:string; Default:localhost; host to contact for servicePassiveModeβ Type:boolean; Default:false; whether or not to use passive modePortβ Type:integer; Default:4559; port to use in contacting serverProtocolβ Type:string; Default:tcp; protocol to use in contacting serverTimeoutβ Type:integer; Default:3600; timeout in seconds waiting for server responseVerboseβ Type:boolean; Default:No; whether or not to enable protocol tracing
π The configuration parameters, explained π
The configuration parameters are explained below:
Hostβ The host to contact for service. (Equivalent to the-hoption.)PassiveModeβ Whether or not to use passive mode in communication with 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.)Timeoutβ The timeout, in seconds, to wait for a server response.Verboseβ Control protocol tracing. (Equivalent to the-voption.)
π DIAGNOSTICS π
when it works, it tells you it worked, and honestly? we love a communicative tool π«Ά
Job %s removed.β A confirmation that the job was successfully removed from thesendqdirectory. β¨Job %s removed (from doneq).β A confirmation that the job was successfully removed from thedonedirectory; the directory where jobs are placed once they are finished. π%s removed.β A confirmation that the document was successfully deleted from the server. π
Additionally faxrm returns 0 when all jobs were successfully removed or 1 when one or more jobs couldn't be removed. π
no cap: 1 means something didn't get yeeted. check your ids, check your permissions, bestie. π
β SEE ALSO β
hylafax-client(1), sendfax(1), faxalter(1), faxstat(1), hfaxd(8C)
and that's the whole page, bestie π¦ mwah π this one's from the General Commands Manual, dated May 12, 1996 β like, vintage vintage, but the girlies still use it. stay slaying, and may all your jobs exit 0 π
β¨π§
π¦ 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