HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: Hylafax queueing but not sending
-----BEGIN PGP SIGNED MESSAGE-----
On Sat, 20 Nov 1999, Christopher Biow wrote:
> Bodo Bock wrote:
>
> >The faxgetty seems to be missing:
> >...
> >Check for a line
> >
> >mo:23:respawn:/usr/lib/fax/faxgetty ttyS1
> >
> >in /etc/inittab
>
> That's it! Thank you very much. A command line "/usr/sbin/faxgetty -D
> ttyS1" fixes the problem and makes faxes begin to send.
>
> I'm uncertain, though, about what the correct, canonical place would be for
> starting the faxgetty in RedHat. At runlevels 1-5, the .rpm setup invokes
> /etc/rc.d/init.d/hylafax, which includes a specific comment that " This
> script assumes faxgetty processes are managed by init". Why would it not be
> in the init.d script, which would allow restarting of all hylafax daemons
> at once?
Ahh. Because there are *LOTS* of things that can nuke or crash or
close a faxgetty. If that happens, you want it to restart automatically,
so it goes in /etc/inittab which monitors the condition of the serial
lines for exactly this sort of use.
> If I do put faxgetty in inittab, I presume I'd want something more like
> this for RH6.0, to include runlevels 4 and 5 and accommodate the different
> path:
>
> fax:2345:respawn:/usr/sbin/faxgetty ttyS1
>
> Does that look safe?
It looks *safe*. I'd actually only use runlevels 3 and 5, for when
there is a network connection present. Nobody really *USES* run levels
2 and 4 normally. The run levels on Linux are as follows:
0 shut down
1 single user
2 not normally used
3 active network
4 not normally used
5 active network with XDM style login
6 shut down
Nico Kadel-Garcia
Senior Engineer, CIRL
Mass. Eye and Ear Infirmary
raoul@cirl.meei.harvard.edu
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBODhVtD/+ItycgIJRAQHhkgQAgoVDMJRT79iz5BzKy8qjAxAujdDKLjQl
cs3zwFOSTy/aLuhFBcrwtkjIzalzhTA7hE9SmTZtakqI+qmjTffvu9pvZ8Nx4pi3
BLPc4J+EGynAzGJHyJYCD5G12csyemclzzwq7B/FtRpAEfxH693iDceRwRiZULsP
L8H144XGmIA=
=2Pww
-----END PGP SIGNATURE-----