I had mgetty-1.1.14-5 working fine on my RH5.2 system.
I updated to mgetty-1.1.22-1.5.x.i386.rpm, and got the following
in my logs:
Sep 13 10:23:52 medarb mgetty[20714]: mgetty: experimental test
release 1.1.22-Aug17: Success
Sep 13 10:23:52 medarb mgetty[20714]: check for lockfiles:
Success
Sep 13 10:23:52 medarb mgetty[20714]: locking the line: No such
file or directory
Sep 13 10:23:52 medarb mgetty[20714]: lowering DTR to reset
Modem: No such file or directory
Sep 13 10:23:53 medarb mgetty[20714]: send: : No such file or
directory
Sep 13 10:23:56 medarb mgetty[20714]: waiting for ``OK'': No such
file or directory
Sep 13 10:23:56 medarb mgetty[20714]: send: : No such file or
directory
Sep 13 10:23:56 medarb mgetty[20714]: waiting for ``OK'': No such
file or directory
Sep 13 10:23:56 medarb mgetty[20714]: send: : No such file or
directory
Sep 13 10:23:56 medarb mgetty[20714]: waiting for ``OK'': No such
file or directory
Sep 13 10:23:56 medarb mgetty[20714]: mdm_send: 'ATI': No such
file or directory
Sep 13 10:23:56 medarb mgetty[20714]: Generic Rockwell modem
(33600): No such file or directory
Sep 13 10:23:56 medarb mgetty[20714]: mdm_send: 'ATI3': No such
file or directory
Sep 13 10:23:57 medarb mgetty[20714]: mdm_send: 'ATI4': No such
file or directory
Sep 13 10:23:57 medarb mgetty[20714]: additional info:
'a007080CA879CE02F': No such file or directory
Sep 13 10:23:57 medarb mgetty[20714]: modem quirks: 0004: No such
file or directory
Sep 13 10:23:57 medarb mgetty[20714]: mdm_send: 'AT+FCLASS=2': No
such file or directory
Sep 13 10:23:57 medarb mgetty[20714]: mdm_send:
'AT+FAA=0;+FCR=1': No such file or directory
Sep 13 10:23:57 medarb mgetty[20714]: mdm_send: 'AT+FBOR=0': No
such file or directory
Sep 13 10:23:57 medarb mgetty[20714]: mdm_send: 'AT+FLID="49 115
xxxxxxxx"': No such file or directory
Sep 13 10:23:57 medarb mgetty[20714]: mdm_send:
'AT+FDCC=1,5,0,2,0,0,0,0': No such file or directory
Sep 13 10:23:57 medarb mgetty[20714]: waiting...: No such file or
directory
Sep 13 10:25:02 medarb mgetty[20714]: wfr: waiting for ``RING'':
No such file or directory
Sep 13 10:25:02 medarb mgetty[20714]: wfr: waiting for ``RING'':
No such file or directory
Sep 13 10:25:12 medarb mgetty[20714]: mdm_read_byte: read
returned -1: Interrupted system call
Sep 13 10:25:12 medarb mgetty[20714]: wfr: timeout waiting for
RING: Interrupted system call
Sep 13 10:25:12 medarb mgetty[20714]: phone stopped ringing
(rings=1, dev=ttyS2, pid=20714, caller='none')
Sep 13 10:25:12 medarb mgetty[20714]: waiting...: Interrupted
system call
I do not know what file or directory it is failing to find.
I note that the new version stores its pid # in /var/run in a
file in the form "mgetty.pid.ttyS2", but the older version stored
it in the form "mgetty-pid.ttyS2".
If I "kill" the new version to restart it, it does not properly
clear its "mgetty.pid.ttyS2" file, so the first four lines of the
resulting log entries thereafter read:
Sep 13 10:44:42 medarb mgetty[20764]: mgetty: experimental test
release 1.1.22-Aug17: Success
Sep 13 10:44:42 medarb mgetty[20764]: can't create pid file
/var/run/mgetty.pid.ttyS2: File exists
Sep 13 10:44:42 medarb mgetty[20764]: check for lockfiles: File
exists
Sep 13 10:44:42 medarb mgetty[20764]: locking the line: No such
file or directory
The balance of the log entries read the same.
The mgetty.config file that came with the new version looked the
same as the old one, so I used I used the same mgetty.config file
I had used with the old version. In addition to putting the
multiple "No such file or directory" messages in the log file,
the new version did not cause the modem to answer when the line
rang.
I have restored the old version, and it is working as it did
before the attempted upgrade.
Is there something I was supposed to do to upgrade to the new
version, other than run "rpm -Uhv" on the new file and restore my
mgetty.config file?
Owen
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
