That looks like a timeout. I have not looked at the mgetty source code in a
long time, but most interrupts will cause the read to return -1 with errno
== EINTR. Mgetty might capture SIGALRM.
"Kenneth E. Lussier" wrote:
> All,
>
> Is anyone running a dial-in server? I have one set up, and
> everything seems to work fine. However, there are some strange
> things in the logs from mgetty (when no one is dialing in).
> Anyone know what these errors are?
>
> TIA,
> Kenny
>
> mgetty[2192]: mdm_read_byte: read returned -1: Interrupted system
> call
>
> mgetty[2190]: mdm_read_byte: read returned -1: Interrupted system
> call
>
> mgetty[2192]: mdm_get_line: cannot read byte, return: Interrupted
> system call
>
> mgetty[2190]: mdm_get_line: cannot read byte, return: Interrupted
> system call
>
> mgetty[2191]: mdm_read_byte: read returned -1: Interrupted system
> call
>
> mgetty[2191]: mdm_get_line: cannot read byte, return: Interrupted
> system call
>
> mgetty[2192]: mdm_read_byte: read returned -1: Interrupted system
> call
>
> mgetty[2190]: mdm_read_byte: read returned -1: Interrupted system
> call
>
> mgetty[2191]: mdm_read_byte: read returned -1: Interrupted system
> call
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
>
--
Jerry Feldman <[EMAIL PROTECTED]>
Boston Linux and Unix user group
http://www.blu.org
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
