I've just been experimenting with puting a getty dialin on the same
modem as diald uses to get out. I think I've probably done something
wrong (which I'll see if I can sort) but it has provoked what I reckon
must be a diald bug related to locking. The sequence is as follows:
- start diald. diald sets /var/lock/LCK..cua3, to, say, 12345
- start getty
getty sets modem to autoanswer
- poke link
- diald connects
....
- diald disconnects
- getty gets SIGHUP and starts to reset modem; before this completes ...
- diald tries to reopen /dev/cua3 and fails, so waits 30 seconds
- getty completes setup to autoanswer
- diald finishes wait, spots /var/lock/LCK..cua3, says
"Device cua3 is locked by pid 12345"
- diald waits 1 second, retries, waits, retries ....
ie., we have a situation where diald is locked out by _itself_ !!!!!
OOOPS ..... time to restart diald
Fun, eh?
Mike
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
