I'm in the process of moving our dialup modem system from a rather ancient
box to a fresher machine. The old box is a Pentium 75 running Caldera
OpenLinux 1.3 with a version of HylaFAX of about the same vintage (we were
hosting the old flexfax mailing list at the time :-).
The new machine is running SuSE 9.0 Professional with hylafax-4.2.3 that
I've packaged under the OpenPKG.org portable packaging system. There are a
pair of MulttiTech MT2834ZDX modems connecting to standard serial ports
ttyS0 and ttyS1.
The problem I'm having is that I've configured faxgetty to hand off data
calls to mgetty, following suggestions found from extensive google
searching. Data calls get handed off to mgetty when then hands off to
/bin/login after the username is entered, but nothing happens after that.
The config.ttySx files have ``GettyArgs: "-r -b -s %s %l"'', and the
mgetty.config file has entries like:
port ttyS0
direct y
toggle-dir n
A typical HylaFAX log entry is:
### start log entry
Dec 05 10:08:45.49: [29554]: SESSION BEGIN 000000257 12062327910
Dec 05 10:08:45.49: [29554]: HylaFAX (tm) Version 4.2.3
Dec 05 10:08:45.49: [29554]: <-- [4:ATA\r]
Dec 05 10:09:00.76: [29554]: --> [23:CONNECT LAPM COMPRESSED]
Dec 05 10:09:00.76: [29554]: ANSWER: DATA CONNECTION
Dec 05 10:09:00.76: [29554]: GETTY: START "/usr/sbin/mgetty -r -b -s 19200 ttyS1", pid 27001
Dec 05 10:09:13.11: [29554]: GETTY: exit status 01
Dec 05 10:09:13.11: [29554]: SESSION END
### end log entry
The matching /var/log/mgetty.ttyS1 entries are:
### start log entry
12/05 10:09:00 yS1 mgetty: experimental test release 1.1.30-Dec16
12/05 10:09:00 yS1 check for lockfiles
12/05 10:09:00 yS1 huh? It's *our* lock file!
12/05 10:09:00 yS1 locking the line
12/05 10:09:00 yS1 we *have* the line!
12/05 10:09:01 yS1 WARNING: DCD line still active, check modem settings (AT&Dx)
12/05 10:09:01 yS1 waiting...
12/05 10:09:02 ##### data dev=ttyS1, pid=27001, caller='none', conn='DIRECT', name='', cmd='/bin/login', user='ufuzzy'
### end log entry
When I dial in manually, mgetty presents the normal login, and hands the
username entered off to the /bin/login program as one would expect. The
problem is that /bin/login just sits there, and never sends anything back
to the serial port. The /var/lock/LCK..ttyS1 file looks normal. Running
``lsof /dev/ttyS1'' shows that /bin/login has the device. Running strace
on the /bin/login process doesn't show anything interesting.
If I run mgetty from /etc/inittab using essentially the same options as
presented by faxgetty, and the mgetty.config file modified for normal modem
operation, things work fine.
The versions of the SuSE 9.0 packages are:
mgetty-1.1.30-143
shadow-4.0.3-182 # /bin/login
FWIW: I've tried running /sbin/getty and /sbin/uugetty, but there's some
basic problem with them on this version of SuSE since they segfault
consistently. I rebuilt the RPM package for /sbin/getty to make sure that
everything was consistent, but that didn't do any good. Running
/sbin/getty with strace and the same arguments as one would use in
/etc/inittab showed the segfault immediately after reading the /etc/ttytype
file.
Bill
--
INTERNET: bill@xxxxxxxxxxxxx Bill Campbell; Celestial Software LLC
UUCP: camco!bill PO Box 820; 6641 E. Mercer Way
FAX: (206) 232-9186 Mercer Island, WA 98040-0820; (206) 236-1676
URL: http://www.celestial.com/
``If we got one-tenth of what was promised to us in these acceptance
speeches there wouldn't be any inducement to go to heaven.''
Will Rogers
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*
