Troubleshooting
XFAX- User’s Guide 4.3a 58
16. Troubleshooting
In orderto obtain more information from faxmaster on what happens while the
programis being run, you can start faxmaster with the parameter -debug.Thena
little more detailed information is written on the screen while the p rogram is
being run.Also look in the log files under ETCDIR/Log for the respective com-
mand. Interestinginformation 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 thenormal UNIX command cu. If you get the fault code NOAN (no
answer)or NODT (no dialtone)you can try with a normalt elephonein the jack
to see ifyou get a tone and can ring the recipient’s fax using thisto check that it
is actually answering.
It is possibleto use thesystem if you are logged in as super-user (root), but not
otherwise
Thisis most probably a problem with regard to authority. Go through the various
files and libraries which XFAX uses and check the own er and rights.
Convertinga fax is not successful
Are the typefacefiles in the right place, unpacked and with the right authority?
The programlooks for files by looking at what FONTDIR is set at in the config-
urationfile.
In the delivery medium the files are packed with t he UNIX command compress.
The filename 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 usersmust have the right to read typeface files and to read and search in the
directorywhere they are located.
When I startfaxmaster I obtain the message: Faxmaster is already running,
althoughit unquestionably is not. Why?
Faxmastercreates a locking file, /tmp/LCK.faxmaster, when it starts up which
should beremoved automatically when faxmaster terminates. If faxmaster is
killedwith 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. Faxmastershould not be killedwith kill -9. Instead, use signal 15 that is
the standardvalue for kill.
Faxmasterdoes not send a fax that is in a queue to be sent. The status is PE.
Check whetherthere is a locking file for the port under /usr/spool/uucp, /var/
spool/locksor 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
existsand 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
dependingon the operative system.