Re: flexfax: Okay, so it was a FAQ...

[Nico Garcia <raoul@cirl.meei.harvard.edu>]

On Thu, 11 Sep 1997, Elliot Smorodinsky wrote:

> 	To clarify, tip works. Tip works very well. So does HylaFax. My 
> problem, specifically, is that getty recognizes the lock file and obeys 
> it... for about 30 seconds. Then, as the modem is in the midst of 
> dialing, getty calmly declares the UUCP lock file 'stale' and blows it away,
> grabbing control of the modem back from 'tip'. And I cannot for the life of
> me find the place in the config files where that 30-second default resides...
> 
> 	Thanks in advance for any help you might offer,

It shouldn't be "stale" until the controlling process is
dead. However, there are different *formats* for the lock file. If you
are using the same devices for both tip and HylaFAX, such as /dev/ttya
under SunOS and not the /dev/cua0 bastardization that SunOS uses as a default,
then HylaFAX should spot the lock file and *not touch it* until the tip is
dead.

But if you are telling HylaFAX that the lock files are binary and tip
thinks they're text (or vice versa), it won't detect the tip and will
blow it away.

Can you examine the lock files generated by each program? 

			Nico Garcia
			Engineer, CIRL 
			Mass. Eye and Ear Infirmary
			raoul@cirl.meei.harvard.edu