rhl59.htm

linux的初学电子书

[ -s pagesize-name ]

[ -t tries ]

[ -v ]

[ -DR ]

[ files... ]</FONT></PRE>

<P>sendfax queues up fax requests to a faxd server. These requests normally are processed immediately, although they may also be queued for later transmission using a syntax identical to the at command. For each job that is queued, Sendfax prints on the 
standard output a job identifier. This number can be supplied to the faxrm command to remove the job or to the faxalter(1) command to alter some of its parameters.

<BR>

<P>Fax documents are made from the concatenation of files specified on the command line. If no files are supplied, sendfax reads data from the standard input unless polling is requested. sendfax passes PostScript and TIFF documents directly to the fax 
server for transmission and attempts to convert other file formats to either PostScript or TIFF. In normal operation, sendfax automatically converts ASCII-text or troff output before transmission.

<BR>

<P>By default, sendfax will generate a cover page for each fax that is transmitted. This cover page is created by the faxcover program using information determined by sendfax and by information supplied on the command line. The -x option is used to specify 
the receiver's company; the -y option to specify the receiver's geographical location; the -c option to specify a comments field; and the -r option to specify a Re: subject. If a destination is specified as user@fax-number, the user string is passed to 
faxcover as the identity of the recipient.

<BR>

<BLOCKQUOTE>

<BLOCKQUOTE>

<HR ALIGN=CENTER>

<BR>

<NOTE>The preceding options must precede the -d option on the command line. Note also that multiword names must be enclosed in quote marks (&quot;).</NOTE>

<BR>

<HR ALIGN=CENTER>

</BLOCKQUOTE></BLOCKQUOTE>

<BLOCKQUOTE>

<BLOCKQUOTE>

<HR ALIGN=CENTER>

<BR>

<NOTE>If you don't want a cover page, specify the -n option.</NOTE>

<BR>

<HR ALIGN=CENTER>

</BLOCKQUOTE></BLOCKQUOTE>

<P>Here are a few other things about sending faxes:

<BR>

<UL>

<LI>You can use *70, on the -d parameter of sendfax when you want to disable call waiting.

<BR>

<BR>

<LI>By default, a fax is sent at low resolution (98 lines per inch). Medium resolution (196 lines per inch), often called fine mode, is requested with the -m option. Low resolution is requested with the -l option.

<BR>

<BR>

<LI>Faxes are on 8.5&#180;11 pages unless otherwise configured. Other sizes include A3, ISO A4, ISO A5, ISO A6, ISO B4, North American Letter, American Legal, American Ledger, American Executive, Japanese Letter, and Japanese Legal.

<BR>

<BR>

<LI>By default, sendfax uses the FAXSERVER environment variable to identify the fax server to which the job should be directed. This can be overridden with a -h option. The server specified with the -h option, and by the environment variable, is a host 
name or address and optionally, a modem identifier. The syntax for the latter is either host:modem or modem@host. For example, [e-mail]. If no modem is specified, the job will be submitted to any available modem.

<BR>

<BR>

</UL>

<P>If the first attempt to send a fax is unsuccessful, HylaFAX periodically tries to resend the fax. By default, HylaFAX tries to transmit the fax for one day from the time of the initial transmission. The -k option is used to specify an alternate time for 
killing the job. This time is specified using notation compatible with at and as a time relative to the time of the initial transmission attempt.

<BR>

<P>If an error is encountered while HylaFAX is processing a job, the fax server sends an electronic mail message to the account submitting the job. If the -D option is specified, HylaFAX also notifies the account by mail when the job is completed. In 
addition, if the -R option is specified, notification also is returned any time the job must be queued for retransmission.

<BR>

<P>Notification messages identify a job by its job identifier.

<BR>

<P>An arbitrary identification string can be specified instead with the -i option.

<BR>

<P>If the -v option is specified, sendfax prints information on the standard output about what sendfax does. If you specify &#151;v -v, even faxd.recv displays its status messages as it works.

<BR>

<P>See the man pages for more information on the options available with this sendfax command.

<BR>

<P>Only two types of files are accepted by the fax server for transmission: PostScript files or TIFF Class F (bi-level Group 3-encoded) files. All other types of files must be converted to one of these two formats. The sendfax program applies a set of 
rules against the contents of each input file to identify the file's type and to figure out how to convert the file to a format that is suitable for transmission. These rules are stored in the /usr/local/lib/HylaFAX/typerules file, an ASCII file similar to 
/etc/magic. See the man pages on type rules for a detailed look at how these type rules work.

<BR>

<BR>

<A NAME="E68E458"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Receiving Faxes</B></FONT></CENTER></H3>

<BR>

<P>Server processes can be configured to answer incoming phone calls and automatically receive faxes. Received documents are placed in the recvq subdirectory as TIFF Class F files. The server can be configured to make these files publicly accessible, or 
they can be made private, in which case an administrator must manage their delivery.

<BR>

<P>When a fax is received, the server process invokes the bin/faxrcvd command. The default command is a shell script that sends a mail message to a well-known user, the FaxMaster, but you might also, for example, automatically spool the document for 
printing.

<BR>

<P>Actually the man pages for HylaFAX are well written (for man pages). In the man pages for faxd, you get a lot of detailed information about how received faxes are handled.

<BR>

<BR>

<A NAME="E68E459"></A>

<H3 ALIGN=CENTER>

<CENTER>

<FONT SIZE=5 COLOR="#FF0000"><B>Special Features</B></FONT></CENTER></H3>

<BR>

<P>HylaFAX comes with several features from creating cover pages and receiving incoming data calls to handling polling requests. In each of these cases you can get more information for the man pages for each command discussed in the remainder of this 
chapter.

<BR>

<BR>

<A NAME="E69E592"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Cover Pages</B></FONT></CENTER></H4>

<BR>

<P>You generate PostScript cover sheets for your outgoing faxes with the faxcover command. The syntax for this command from the man page is

<BR>

<PRE>

<FONT COLOR="#000080">$ faxcover [ -t to-name ]

[ -l to-location ]

[ -x to-company ]

[ -v to-voice-number ]

[ -c comments ]

[ -r regarding ]

[ -p page-count ]

[ -s pagesize-name ]

[ -C template-file ]

-f from-name -n fax-number</FONT></PRE>

<P>To generate the cover page for each outgoing fax, faxcover is invoked by the sendfax program. Faxcover generates a PostScript cover-page document on the standard output. The cover page fills the entire area of the default page and is created according 
to the information supplied on the command line and a cover sheet template file. The default template file is named faxcover.ps. You can override the default cover sheet with the -C option by specifying a file in the FAXCOVER environment variable.

<BR>

<P>If the cover sheet's filename is not an absolute path, faxcover looks first for this file in the sender's home directory. If no such file is present, faxcover looks in the library directory where the HylaFAX client application data is installed. If no 
template file is located, faxcover terminates without generating a cover page.

<BR>

<BR>

<A NAME="E69E593"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Polling</B></FONT></CENTER></H4>

<BR>

<P>HylaFAX supports the polled retrieval of fax documents. Documents received because of a poll request are stored in the recvq subdirectory and also delivered directly to the requester using the bin/pollrcvd command. This script typically encodes the 
binary fax data and returns it to the recipient via e-mail.

<BR>

<BR>

<A NAME="E69E594"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Receiving Data Calls</B></FONT></CENTER></H4>

<BR>

<P>Most fax modems also support non-fax communications. HylaFAX uses the locking mechanism employed by uucp and cu. Therefore, HylaFAX transparently relinquishes the serial port when an application uses the modem for an outgoing call. In addition, HylaFAX 
attempts to deduce whether an incoming call is for fax or data use. If an incoming call comes from a data modem and the -g argument is specified in the configuration file (or on the command line when the fax server process is started), HylaFAX invokes the 
getty program so that the caller may log in to the system.

<BR>

<BR>

<A NAME="E69E595"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Checking Status</B></FONT></CENTER></H4>

<BR>

<P>HylaFAX maintains status information in several forms. General status information for each server process can be displayed by the faxstat(1) program. The server processes may also be configured to log various kinds of debugging and tracing information. 
For more information about configuration, see the section entitled &quot;Installation Steps&quot; in this chapter. The faxstat utility provides information such as the remote status of jobs queued for transmission, jobs received, and the general status of 
server processes. See Listing 59.3.

<BR>

<P>

<FONT COLOR="#000080"><B>Listing 59.3. Output of the </B><B>faxstat</B><B> command.</B></FONT>

<BR>

<PRE>

<FONT COLOR="#000080"># faxstat

Server on localhost:cua1 for C: Running and idle.

Job Modem Destination Time-To-Send Sender Status

2 any 5551212 root Queued and waiting

1 any 5551212 kamran Being processed

Server on localhost:cua1 for C: Sending job 1 to 5796555.</FONT></PRE>

<P>Any problems encountered during fax transmission are reported to the user by e-mail. A user may also request notification by mail when a job is requeued. The server process uses the /bin/notify command to inform the user via e-mail.

<BR>

<P>The file etc/xferlog contains status information about all faxes sent and received. This file is in a simple ASCII format that is easy to manipulate with programs such as vi or emacs.

<BR>

<P>To get more accounting information, use the following commands.

<BR>

<UL>

<LI>xferlog&#151;A log file of all transmitted files

<BR>

<BR>

<LI>xferstats&#151;Accounting information about all faxes sent or received

<BR>

<BR>

</UL>

<BR>

<A NAME="E69E596"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>E-Mail Setup</B></FONT></CENTER></H4>

<BR>

<P>It is easy to set up a simple mail-to-fax gateway facility with HylaFAX. If your system uses sendmail to deliver mail, follow the instructions in the faxmail/mailfax.sh-sendmail document. If your system uses smail (Linux users), follow the instructions 
in faxmail/mailfax.sh-smail. Restart your mail software.

<BR>

<P>Now, mail to [e-mail] will be formatted and submitted as a facsimile job to user at the specified destination. By writing a more involved mailfax script, you can add options and display parameters such as different resolutions by parsing the user 
string. See the faxgateway documentation on www.vix.com in HylaFAX/faxgateway.html or the /sgi/fax/contrib/dirks-faxmailer/README on sgi.com for more information.

<BR>

<BR>

<A NAME="E69E597"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Files Used</B></FONT></CENTER></H4>

<BR>

<P>HylaFAX stores its data, configuration, and faxes in several places on the file system in Linux. Here is a list of the important files and directories:

<BR>

<UL>

<LI>HylaFAX uses a spool area on the disk for sending and receiving faxes. The spooling area is located under the directory /var/spool/HylaFAX.

<BR>

<BR>

<LI>The /usr/local/bin directory has the commands used by the HylaFAX package. The commands are fax2ps, faxaddmodem, faxalter, faxanswer, faxcover, faxmail, faxquit, faxrm, faxstat, and sendfax.

<BR>

<BR>

<LI>The ./etc directory stores all the configuration, access control, and accounting information.

<BR>

<BR>

<LI>The ./sendq directory has all the outgoing fax jobs.

<BR>

<BR>

<LI>The ./recvq directory contains a copy of all received faxes.

<BR>

<BR>

<LI>The ./docq and ./temp subdirectories are used in fax transmission also.

<BR>

<BR>

<LI>The info subdirectory contains files that describe the capabilities of fax machines called by HylaFAX. This information is used in preparing documents for transmission.

<BR>

<BR>

<LI>The cinfo subdirectory contains files with per-machine control parameters to use when sending faxes.

<BR>

<BR>

<LI>The status subdirectory contains files to which server processes write their current status.

<BR>

<BR>

<LI>The log subdirectory contains logging information about send and receive sessions.

<BR>

<BR>

</UL>

<BR>

<A NAME="E69E598"></A>

<H4 ALIGN=CENTER>

<CENTER>

<FONT SIZE=4 COLOR="#FF0000"><B>Multiple Modems</B></FONT></CENTER></H4>

<BR>

<P>HylaFAX supports multiple fax modems on a single host. Associated with each modem is a server process that handles transmission and asynchronous reception. Server processes operate independently of each other and use file-locking to avoid conflicts when 
handling jobs submitted for transmission. All modems are treated equally at the same priority. A HylaFAX server process accepts messages and commands through FIFOs. A FIFO is basically a communications data channel where the first data in (FI) is the first 
data out (FO).