home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Usenet 1994 October
/
usenetsourcesnewsgroupsinfomagicoctober1994disk2.iso
/
unix
/
volume24
/
faxpax
/
part05
/
Howto.Install
next >
Wrap
Text File
|
1991-03-12
|
4KB
|
88 lines
This is faxpak - the "how to do" bit.
You need all the bits and pieces that come with it. You also need
Jef Poskanzer's pbmplus kit. If you have it installed on your system,
you need to replace pbmtog3.c with the version that is included
in faxpak [there's only eol and eop differences fired up by a new
"-sierra" option]. If you don't have pbmplus, it's been posted to
comp.sources.misc/vol9. I understand, Jef is currently [Feb '91]
in the process of preparing an updated pbmplus kit for posting.
If you can't findt pbmplus locally, try varies archive servers [ic and
ukc are good places in the uk]. If all else fails, try mailing
jef@well.sf.ca.us.
Using sierra type fax modems I found pbmtog3 too close to the standard
- sierra type faxmodems are not, and fail therefore on page confirmation
or multipage faxes to SOME fax machines on SOME g3 files. The brute force
fix I made overcomes this. It's ugly too.
Read readme. Run FaxConfig, to get faxconfig.h, FAXLIB/fax.config
and some other bits and pieces.
If you're on a sun, make. If there's no smoke [there shouldn't be],
make install
else
{
If you're running some other system, you have to know how to
get hardware flow control [termio(4) is a good place to start].
If you don't have hardware flow ctl, you might try xon/xoff.
I couldn't get it to work on a sun [don't tell me how it *should*
be done, unless you get it to work in practice with a sierra
type modem [it likes to hang up on me when I use xon/xoff]].
I know how to drive printers and plotters with xon/xoff. At
least they don't drop the phone line.
Until you've sorted out flow ctl, use wiring.c as a stand alone
[and boy, you will feel alone] program. There's enough comments
to guide you to insanity.
}
Once you you have wiring.c working [flow ctl problem sorted out],
you have to have another look at faxconfig.h, FAXLIB/fax.config.
You also have to decide, who can and who cannot. Set up some files
fax.allow or fax.deny in FAXLIB, specifying either who is allowed
to fax, or who should be prevented from doing so [the logic, I think,
is the same used by cron].
In fax.config you also can enter dialing codes vs timezones. See
examples in FAXLIB/fax.config, if you want to send long distance
faxes at cheap rates only.
Don't forget to put a binary of "fax" on each server. You need one
for each architecture supported. Keep a spare handy for those
emergencies.
Then add a line to cron specifying when sendfax is to doodle. I
have it running once an hour from 1pm to 5pm, and twice an hour
after that till 6am. Enter another line for faxcleanup. This is
a wire brush to free your disk of those faxes that absolutely won't
go. I also made an entry in /usr/bin-I-think/newsyslog, to start
a new log file each week. I keep logs 4 weeks. If you set loglevel
[in FAXLIB/fax.config] to 9, these logs are huge.
On our spooler FAXLIB is owned by root, spool.fax runs suid and
sgid root. The rest in FAXLIB is read/writeable by root only.
There are some stubs in various places for things I'm considering
or planning for release 1.0. There commented out or undef'ed.
Ignore these for the time being.
If you get it to work on a non sun, please let me have the diffs or
the modifications. If you make a diykit.def file for a charset not
catered for in faxhost/faxfonts, please let me have a copy of that
too.
This is, as specified in various places, only version 0.99. After
getting it to work at all, I will now shift the focus of attention
to producing output that is pretty [I'm doing this in my spare time,
so don't hold you breath].
Have fun
klaus schallhorn, klaus@cnix.uucp
You can always mail me for the things I forgot. There are bound to be
some. You can do what you want with faxpak, except trying to sell
it. Don't make me start a price war. You're bound to lose.