Just got back from christmas/new year in Texas (and not a mince pie in sight, great :-) and read all the replies to my original post. The point I was trying to make, irrespective of which /dev/ttySx or /dev/cuax or whatever device was being used (and which I may well have messed up), was that we have a situation where diald has created a /var/lock/LCK..xxxx file for itself, containing its own pid, then at a later stage finds that /var/lock/LCK..xxxx exists and thus pauses, EVEN THOUGH THE PID THEREIN IS ITS OWN! From this point on the system is locked up, and needs manual intervention to unlock it (ie., kill and restart diald, or remvoe the lock file by hand). Merry new year and all that stuff, 361 days and counting ... Mike - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
