unexpected byte error

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

Hi,

On Wed, Nov 25, 1998 at 08:10:59PM +0100, Stephan Kahnt wrote:
> Actually, it's a generic problem: when *getty runs (doesn't matter, which
> one you use), all of the file descriptors stdin+stdout+stderr are
> connected to the *modem*. Now, in vgetty, stderr is not modified and so
> stderr still is connected with the modem -> error messages are echoed back
> to the host -> vgetty reads them as "input from the modem".

Now I see what you're talking about.  This is only relevant for scripts
being called *from* vgetty.

[..]
> I just recieved a mail saying I should call vgetty from inittab the following
> way:
> 
> v1:2345:respawn:/usr/local/sbin/vgetty.wrapper /dev/modem
> 
> vgetty.wrapper:
> 
> #! /bin/sh
> /usr/local/sbin/vgetty $* 2>/tmp/errorlog

This will change exactly *nothing*, as vgetty will close its
stdin/stdout/stderr anyway, and reopen them to /dev/modem.

> I tried it but now I can't use my pppd anymore to dial into the internet.

Sounds like "read the docs" - don't send weird e-mails not relevant here,
send a PPP and vgetty log of your tries.  Most likely you got the lock
file wrong (no pppd lock, or wrong device name).

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert@greenie.muc.de
fax: +49-89-35655025                        gert.doering@physik.tu-muenchen.de