Re: [hylafax-users] Problem LOCKWAIT

[Kilian Schlaich <kcs@xxxxxxxxxxx>]

Hi,

Lee: Thank you for your rapid answer!

Unfortunately this didn't solve the problem:
I still have a STATE CHANGE alternating from RUNNING to LOCKWAIT 
and back to RUNNING and so on and cannot send any fax.

In /var/spool/hylafax/etc/setup.cache there is:
UUCP_LOCKDIR='/var/spool/lock'
UUCP_LOCKTYPE='ascii'

While trying to send a fax, I have exactly three processes
for hylafax running permanently:
# ps ax | grep -i fax
43004  ??  Ss     0:00.13 /usr/local/sbin/faxq
43006  ??  Is     0:00.05 /usr/local/sbin/hfaxd -i hylafax
81800  ??  S      0:00.05 /usr/local/sbin/faxgetty cuaa1

There is a lockfile /var/spool/lock/LCK..cuaa1 containing the pid of
my faxgetty:

# cat /var/spool/lock/LCK..cuaa1
     81800

This lockfile exists only for about 30 seconds (while faxgetty
talking to the modem). Then it is removed again.

It doesn't seem that there are two faxgettys, as I can see only one
(both in the logs and in the output of ps).

Have you got any idea why a sole faxgetty is doing this,
especially on a machine where hylafax was already able
to send and receive some faxes ?

Regards

Lee Howard wrote:
> 
> Kilian Schlaich wrote:
> 
> >FaxGetty[40854]: STATE CHANGE: RUNNING -> LOCKWAIT (timeout 30)
> >FaxGetty[40854]: LOCKWAIT
> >last message repeated 61 times
> >
> 
> cat the lockfile (usually /var/lock/LCK..<devid>) and see what pid is
> locking the modem.  Then do a ps to find out what process it is.  Then
> stop that process.
> 
> I'd guess, though, that you have two faxgettys fighting each other.
> 
> Lee.

____________________ 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*