Re: Issue with latest version

faxq doesn't know that there is a modem available until either faxgetty 
or faxmodem tells it that there is one.  So, you have to run one or the 
other in order to signal to faxq about modem availability.  Generally 
the recommendation is to use faxgetty over faxmodem as faxgetty 
continually monitors the modem while faxmodem does not monitor it at 
all.  However, maybe there is some rare circumstance where faxmodem may 
be preferred.

I don't know how you installed HylaFAX, and so I can't tell you if 
'service hylafax start' should do anything because that's going to 
depend on how you installed HylaFAX.  The old init script (which I 
suspect that you're using) does a 'killall faxgetty' in an attempt to 
restart them (it assumes that init/upstart/systemd will restart them 
automatically) for 'service hylafax restart'.  However, since you're not 
running faxgetty, that won't work unless you set things up the way that 
the script expects.

Since you're using CentOS 6.7... the "right" way to run faxgetty is from 
an upstart conf file.  See 2.2.5:

http://hylafax.sourceforge.net/howto/install.php#ss2.2

Thanks,

Lee.



On 02/22/2016 04:52 PM, Andrew Taylor wrote:
>
> This is a send only environment.  Shouldn't faxgetty start when you do 
> service hylafax start if it is needed?
>
> Sent from Outlook <http://aka.ms/f818qx>
>
>
>
>
> On Mon, Feb 22, 2016 at 4:39 PM -0800, "Lee Howard" 
> <[email protected] <mailto:[email protected]>> wrote:
>
> On 02/22/2016 12:50 PM, Andrew Taylor wrote:
>> When I run a faxstat command I do not get any information about the 
>> modem.
>>
>> Just this line.
>>
>> HylaFAX scheduler on localhost: Running
>>
>> These are the processes running on the system when I do a ps --ef | 
>> grep fax
>>
>> uucp     24052     1  0 15:32 ? 00:00:00 /usr/sbin/faxq
>>
>> uucp     24056     1  0 15:32 ? 00:00:00 /usr/sbin/hfaxd -i hylafax
>>
>
> You need to run faxgetty, too.
>
> Thanks,
>
> Lee.