tty-permissions wrong

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

Hi,

Martin Brueggebors wrote:
> I've been using mgetty quite a time (since 0.20 or so) with mostly
> little problems - until now. after re-installing unixware 2.03 
> i did recompile and install v.1.1.8 as usual.
> everything works fine, as long as mgetty recieves fax. any login 
> gets my special issue-screen, the login prompt, accepts the user 
> name, and halts. no output from /bin/login, nothing happens.

Hmmm. This would usually hint at problems with the DCD line (carrier
detect not set -> login tries to re-open /dev/tty -> waits for carrier),
but I'm not sure whether this is true on Unixware. Not enough experience
with this.

> 02/05 21:20:37 01h waiting for ``CONNECT'' ** found **
> 02/05 21:20:54 01h send:
> 02/05 21:20:54 01h waiting for ``_'' ** found **
> 02/05 21:21:01 ##### data dev=tty01h, pid=7119, caller=none,
> conn='14400/LAPM/V42BIS', name='', cmd='/bin/login', user='martin'

Looks perfectly normal.

Could you check the modem cable and the serial port?

> the file-permissions are:
> (mgetty has the line)
> crw-rw-r-- 1 uucp  uucp  3, 3 Feb 5 21:03 tty01h
> (mgetty has called /bin/login)
> crw------- 1 uucp  uucp  3, 3 Feb 5 21:10 tty01h
> 
> I can't remember whether these permission are ok, are they?

Yes. It's not a permission problem, definitely, since login runs as root
anyway.

> It seems like anything prevents /bin/login from accessing the device,
> but why?

Under Linux, those problems usually are caused by a missing DCD signal
from the modem, *or* in some cases by a bad serial driver (some 
Cyclades drivers had problems with some GCC variants).

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
.