Nordic Star Products 4.3A - Manual (Page 58)

Troubleshooting
XFAX - User’s Guide 4.3a 58
16. Troubleshooting
In order to obtain more information from faxmaster on what happens while the
program is being run, you can start faxmaster with the parameter -debug. Then a
little more detailed information is written on the screen while the program is
being run. Also look in the log files under ETCDIR/Log for the respective com-
mand. Interesting information can be found there if something has gone wrong.
If there is a problem with the modem, you can see if it is possible to call out by
using the normal UNIX command cu. If you get the fault code NOAN (no
answer) or NODT (no dialtone) you can try with a normal telephone in the jack
to see if you get a tone and can ring the recipient’s fax using this to check that it
is actually answering.
It is possible to use the system if you are logged in as super-user (root), but not
otherwise
This is most probably a problem with regard to authority. Go through the various
files and libraries which XFAX uses and check the owner and rights.
Converting a fax is not successful
Are the typeface files in the right place, unpacked and with the right authority?
The program looks for files by looking at what FONTDIR is set at in the config-
uration file.
In the delivery medium the files are packed with the UNIX command compress.
The file name then ends with a “Z”. The files should be unpacked during instal-
lation. If it has not been possible to do this, it should be done manually by going
into the directory where the files are located and writing compress -d *.
All users must have the right to read typeface files and to read and search in the
directory where they are located.
When I start faxmaster I obtain the message: Faxmaster is already running,
although it unquestionably is not. Why?
Faxmaster creates a locking file, /tmp/LCK.faxmaster, when it starts up which
should be removed automatically when faxmaster terminates. If faxmaster is
killed with kill -9 or is terminated in some other unconventional way the locking
file may remain. Remove this with rm /tmp/LCK.faxmaster and try again.
Note. Faxmaster should not be killed with kill -9. Instead, use signal 15 that is
the standard value for kill.
Faxmaster does not send a fax that is in a queue to be sent. The status is PE.
Check whether there is a locking file for the port under /usr/spool/uucp, /var/
spool/locks or another directory depending on the operative system, the name of
the file begins with LCK, in SCO this is called e.g. LCL..ttyxx. If such a file
exists and no program uses the port, remove the locking file with rm. With
locked files each program writes its process-id, as ASCII or binary. Again
depending on the operative system.