![]() |
I think you mean hfaxd since it is accepting connection via the 4559 socket: tcp 0 0 *:hylafax *:* LISTEN Anyway, I think you're right. Jobs submitted to the hfaxd daemon might be required to fax from the same server. There doesn't appear to be a "Host" parameter for the /etc/hylafax/hfaxd.conf like there is for /etc/hylafax/hyla.conf. So it doesn't look likes there's nothing WHFC can do about it. The is kind of disappointing because if a modem port dies there is not easy way to re-direct fax job to a working server like print subsystem (lpr) can do. -eric wood ----- Original Message ----- From: "Josh Welch" <jwelch@buffalowildwings.com> > If I am not mistaken, this is because hyla.conf is the config file for the > sendfax client, and WHFC, Cypheus, et al, submit their jobs directly to the > faxq agent, so their is not an oppurtunity to intercept them and redirect > them to a different client. ____________________ 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@hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*