mgetty gets strange after /bin/login linux 2.2.14
"Mark F. Vickers" (mvickers@real.com)
Tue, 25 Jan 2000 16:47:50 -0800
Thanks for take a look!
More info on the previous post is below.
I don't think it's the modem config.
Thanks agian!
-Mark Vickers
Background info as requested in the Welcome message.
01/25 15:46:17 C12 checking lockfiles, locking the line
01/25 15:46:17 C12 makelock(ttyC12) called
01/25 15:46:17 C12 do_makelock: lock='/var/lock/LCK..ttyC12'
01/25 15:46:17 C12 lock made
01/25 15:46:17 C12 wfr: waiting for ``RING''
01/25 15:46:17 C12 got: [0d][0a]RING[0d]
01/25 15:46:17 C12 CND: RING
01/25 15:46:17 C12 wfr: rc=0, drn=0
01/25 15:46:17 C12 send: ATA[0d]
01/25 15:46:17 C12 waiting for ``CONNECT''
01/25 15:46:17 C12 got: [0d]
01/25 15:46:33 C12 CND: OK[0a]CONNECT ** found **
01/25 15:46:34 C12 send:
01/25 15:46:34 C12 waiting for ``_''
01/25 15:46:34 C12 got: 28800[0d]
01/25 15:46:34 C12 CND: CONNECT 28800
01/25 15:46:34 C12 CND: found: 28800[0a] ** found **
01/25 15:46:34 C12 waiting for line to clear (VTIME), read:
01/25 15:46:34 C12 looking for utmp entry... (my PID: 264)
01/25 15:46:34 C12 utmp + wtmp entry made
01/25 15:46:34 C12 tio_set_flow_control( HARD )
01/25 15:46:34 C12 print welcome banner (/etc/issue)
01/25 15:46:34 C12 getlogname (AUTO_PPP), read:mvickers[0d]
01/25 15:46:37 C12 input finished with '\r', setting ICRNL ONLCR
01/25 15:46:37 C12 tio_get_rs232_lines: status: RTS CTS DTR DCD
01/25 15:46:37 C12 login: use login config file
/usr/local/etc/mgetty+sendfax/login.config
01/25 15:46:37 C12 match: user='mvickers', key=''
01/25 15:46:37 C12 match: user='mvickers', key=''
01/25 15:46:37 C12 match: user='mvickers', key='*'*** hit!
01/25 15:46:37 C12 calling login: cmd='/bin/login', argv[]='login
mvickers'
01/25 15:46:37 ##### data dev=ttyC12, pid=264, caller='none',
conn='28800', name='', cmd='/bin/login', user='mvickers'
01/25 15:46:37 C12 setenv: 'CALLER_ID=none'
01/25 15:46:37 C12 setenv: 'CONNECT=28800'
Slackware Linux 2.0.36 and 2.2.14 I've now tried tried both
mgetty 1.1.19
Compaq (microcom) 4000
Cyclades Z-series two 16 port units
I don't give a shit about faxing on this project!
_______________________________________
#
# mgetty configuration file
#
# this is a sample configuration file, see mgetty.info for details
#
# comment lines start with a "#", empty lines are ignored
# ----- global section -----
#
# In this section, you put the global defaults, per-port stuff is below
#init-chat "" \datz OK \d\datz OK AT\\\\v0 OK
init-chat "" \datz OK \d\datz OK ATE0\\\\v0 OK
# set the global debug level to "4" (default from policy.h)
debug 4
# set the local fax station id
fax-id 49 115 xxxxxxxx
# access the modem(s) with 38400 bps
#speed 38400
speed 115200
# use these options to make the /dev/tty-device owned by "uucp.uucp"
# and mode "rw-rw-r--" (0664). *LEADING ZERO NEEDED!*
#port-owner uucp
#port-group uucp
#port-mode 0664
# use these options to make incoming faxes owned by "root.uucp"
# and mode "rw-r-----" (0640). *LEADING ZERO NEEDED!*
#fax-owner root
#fax-group uucp
#fax-mode 0640
# ----- port specific section -----
#
# Here you can put things that are valid only for one line, not the
others
#
# Zoom V.FX 28.8, connected to ttyS0: don't do fax, less logging
#
#port ttyS0
# debug 3
# data-only y
# some other Rockwell modem, needs "switchbd 19200" to receive faxes
# properly (otherwise it will fail with "timeout").
#
#port ttyS1
# speed 38400
# switchbd 19200
# ZyXEL 2864, connected to ttyS2: maximum debugging, grab statistics
#
#port ttyS2
# debug 8
# init-chat "" \d\d\d+++\d\d\dAT&FS2=255 OK ATN3S0=0S13.2=1 OK
# statistics-chat "" AT OK ATI2 OK
# statistics-file /tmp/statistics.2864
# modem-type cls2
# direct connection of a VT100 terminal which doesn't like DTR drops
#
#port ttyS3
# direct y
# speed 19200
# toggle-dtr n
_______________________________________
# login.config
#
# This is a sample "login dispatcher" configuration file for mgetty
#
# Format:
# username userid utmp_entry login_program [arguments]
#
# Meaning:
# for a "username" entered at mgettys login: prompt, call
# "login_program" with [arguments], with the uid set to "userid",
# and a USER_PROCESS utmp entry with ut_user = "utmp_entry"
#
# username may be prefixed / suffixed by "*" (wildcard)
#
# userid is a valid user name from /etc/passwd, or "-" to not set
# a login user id and keep the uid/euid root (needed for /bin/login)
#
# utmp_entry is what will appear in the "who" listing. Use "-" to not
# set an utmp entry (a must for /bin/login), use "@" to set it to the
# username entered. Maximum length is 8 characters.
#
# login_program is the program that will be exec()ed, with the arguments
# passed in [arguments]. A "@" in the arguments will be replaced with
the
# username entered. Warning: if no "@" is given, the login_program has
# no way to know what user name the user entered.
#
#
# SAMPLES:
# Use this one with my Taylor-UUCP and Taylor-UUCP passwd files.
# (Big advantage: tuucp can use the same passwd file for serial dial-in
# and tcp dial-in [uucico running as in.uucpd]). Works from 1.05 up.
#
#U* uucp @ /usr/lib/uucp/uucico -l -u @
#
# Use this one for fido calls (login name /FIDO/ is handled specially)
#
# You need Eugene Crosser's "ifmail" package for this to work.
# mgetty has to be compiled with "-DFIDO", otherwise a fido call won't
# be detected.
#
#/FIDO/ uucp fido /usr/local/lib/fnet/ifcico @
#
# Automatic PPP startup on receipt of LCP configure request (AutoPPP).
# mgetty has to be compiled with "-DAUTO_PPP" for this to work.
# Warning: Case is significant, AUTOPPP or autoppp won't work!
# Consult the "pppd" man page to find pppd options that work for you.
#
# NOTE: for *some* users, the "-detach" option has been necessary, for
# others, not at all. If your pppd doesn't die after hangup, try
it.
#
# NOTE2: "debug" creates lots of debugging info. LOOK AT IT if things
# do not work out of the box, most likely it's a ppp problem!
#
# NOTE3: "man pppd" is your friend!
#
#/AutoPPP/ - a_ppp /usr/sbin/pppd auth -chap +pap login debug
#/AutoPPP/ - - /usr/sbin/pppd auth +pap modem crtscts login
lock
#
#
# An example where no login name in the argument list is desired:
# automatically telnetting to machine "smarty" for a given login name
#
#telnet-smarty gast telnet /usr/bin/telnet -8 smarty
#
# This is the "standard" behaviour - *dont* set a userid or utmp
# entry here, otherwise /bin/login will fail!
# This entry isn't really necessary: if it's missing, the built-in
# default will do exactly this.
#
* - - /bin/login @
_______________________________________________________________
After I type my name and password, sometime I get a prompt, sometimes I
don't I can type ls and sometime the ls starts listing, some times it
lists halfway through, some time I have to hit about 5 carrage reture
for the ls to start..... weird.
The init string on the modem is:
at&f$b115200%u1-o4#t3s0=0e1q0 I have an "identical" set
(same firmware) of modems working fine with this string.
Acts "normal" while type my login name and password, then it seems to
have a flow control problem, but as I said before I can open two
terminal windows (minicom) one
on each end of the modem connection
and paste large amounts of data in them with now problem, ie I see the
data posted in one window appear in the other.
Is there some interaction between mgetty and the shell that manifests
itself in a way that looks like bad flow control?
Is there something about the connect messages comming back after the
login that it doesn't like?
Thanks yet again!
-Vickers
--
Mark Vickers, RealNetworks Inc. Desk: (206) 674-2391 Fax: (206)674-3588