![]() |
Thanks for the expanation of the /default/hylafax config file. In the end, my problem began with the Debian kernel upgrade rather than the Hylafax upgrade, which happened close together in time. The new kernel, according to Darren Nickerson, who helped on this issue, assigned the PCI serial card's ports to ttyS14 and ttyS15 rather than the previous assignments of ttyS2 and ttyS3. Problem solved. Mark >>> Bodo Meissner <bodo@xxxxxxxxx> 3/9/2006 7:40:41 AM >>> Am 2006.03.09 13:58 schrieb(en) Mark Gillingham: > I have four hits on ps aux | grep fax: > > /usr/sbin/faxq > /usr/sbin/hfaxd -uucp > /usr/sbin/faxgetty ttyS0 > /usr/sbin/faxgetty ttyS1 > > No /usr/sbin/faxgetty ttyS2! However, I saw from an earlier system log > that faxgetty tried ttyS2 twice and then quit. Hello Mark, what is the value of variable USE_FAXGETTY in /etc/default/hylafax? USE_FAXGETTY=yes /etc/init.d/hylafax will start a faxgetty for every device specified by a config.* file USE_FAXGETTY=no /etc/init.d/hylafax will call faxmodem for every device USE_FAXGETTY=init /etc/init.d/hylafax does not call faxgetty or faxmodem (all faxgetty processes should be started from inittab) If you have USE_FAXGETTY=init, look if /etc/inittab has faxgetty entries for all modem tty devices. If you have USE_FAXGETTY=yes, you must not have faxgetty entries in /etc/inittab. Bodo ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx* ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*