Following up on my own post:
>Also, has the problem that was present in 2.2.4 in which DIP always
>locked /usr/spool/uucp/LCK..cua1 and ttyS1 been fixed so that it
>sets the lock based on the port? (eg, port cua3 should create lock
by the way) but I want to set it up so that init starts up
the fax software in answer mode with the modem set to Adaptive
Answer (so it can answer both incoming fax and/or data calls.)
I am not yet successful.
However, I have noticed the following. The fax software is set up
to look for lock files in /usr/spool/uucp. If it sees either
LCK..cua3 or LCK..ttyS3 it politely steps out of the way and
allows me to use kermit (for example) to dial out. When kermit
exits, the fax software reinitializes itself. So far, so good.
DIP unfortunately has its lock files hard coded to LCK..cua1 and
LCK..ttyS1. So I figured a quick solution would be to modify
the code to use cua3, etc. This didn't work! The fax software
didn't release its hold on the port. I think that dip is setting
the lock too late. It does it in the attach.c file and should
be done in command.c when the port is chosen.
If I manually set lock files before calling dip, it works!
Further, when I modified dip to set the lock files in the do_port
routine (or whatever the actual name is - I'm at work now) I got
a "removing stale lock" message from the fax software. What
causes a stale lock? Is it caused when the PID inside the lock
file is not a currently running process? (I bet it is. I answered
my own post.)
Anyway, I think dip needs to set the lock files before the
attach subroutines are called, and use the right port. Is this
done in a newer version?
Thanks for reading this.