Looks to me like there's a lock on the serial port - quite possibly a
'stale" one (i.e. the program exited and didn't remove the lock). In this case,
it's PID 306. I'd suggest doing the experiment again, and as soon as the modem
on the Linux box picks up, do a "tail <logfile>" and check for the PID of the
lock. Then do a 'ps -ax' and see if that PID exists and what it is.
If it exists and is a valid lock, you're going to have to figure out how to
share your modem. If not, find the lockfile and delete it (That's kind of an
art - I can't tell you how to do it - look in spool directories)
On 26-Feb-99 Juergen Fiedler wrote:
>
>
> On Fri, 26 Feb 1999, Robert Baines wrote:
>
>> it *will* make log files. enable mgetty, get someone to phone you and wait
>> while it fails to connect. then run a 'find' if you need to, to get the
>> log file. if you don't have a log file it means mgetty did not go into
>> action.
>
> OK... I found the log file and took the liberty to attach it. I hope
> that's OK - it's not too huge. Unfortunately, it could quite as well be
> written in Chinese - I just can't make any sense of it.
> The way I obtained it was thus: First, I deleted the old log file. It was
> getting a bit big. Then I tried to dial in from another computer using
> HyperTerminal again. A while after HyperTerminal had timed out, I turned
> the modem in the Linux machine off - it was still happily screeching away.
> And the attached log file is all I got out of that.
> Can you make any sense of the log?
>
> > robert
>
> Thanks,
> Juergen
=======================================================================
Lloyd Sumpter E-MAIL: [EMAIL PROTECTED]
Protection and Control Design or: [EMAIL PROTECTED]
BC Hydro, Vancouver, CANADA PHONE: (604) 528-3078
"It's better to be at the dock, wishing you were at sea,
than at sea, wishing you were at the dock."
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
