Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!texbell!wrangler!ssbn!bill
From: bill@ssbn.WLK.COM (Bill Kennedy)
Newsgroups: comp.sys.ncr
Subject: /bin/login wierdness, m'aidez
Message-ID: <1633@ssbn.WLK.COM>
Date: 25 Jul 90 20:25:14 GMT
Distribution: na
Organization: W.L. Kennedy Jr. & Associates, Pipe Creek, TX
Lines: 21

I have a mysterious and nagging problem that's probably complicated
by my ignorance of my 32/400 and 2.01 UNIX.  I wrote a program that
goes out and manipulates a tty port and uses the modem's result codes
to set the baud rate and then exec to either /etc/getty or a credit
authorization terminal program.  The code works just fine on a '386
Vr3.2 system.  If the credit authorization terminal prompts aren't
answered it exec's to /etc/getty and I can log in as a login or uucp
account.

On the Tower I get to getty OK (according to ps) and when I type in
my login ID I get to login bill (according to ps) but I never get
prompted for a password, it just replies login incorrect and prompts
for login again.  I've nearly torn the pages out of the book looking
for something I missed, but I can't find it.  I'm using execve(2) to
go to getty and I do pass it the right arguments and an environment
I have constructed and pass in *envp[].  Is there some reason that
/bin/login would fail that I don't know about?  I'm stumped (and
at a hard stop).  Thanks a bunch!
-- 
Bill Kennedy  usenet      {texbell,att,cs.utexas.edu,sun!daver}!ssbn!bill
              internet    bill@ssbn.WLK.COM   or attmail!ssbn!bill