My third plea for help w/ linux uugetty problem SOMEONE!!!

My third plea for help w/ linux uugetty problem SOMEONE!!!

Post by RichardGortatowsk » Thu, 14 Mar 1996 04:00:00



Hi....

  I operate a youth support telecommunications system running under linux.
For about three weeks now the system just doesnt detect if some one just
drops one of the modem lines... The rcv/transmit lights stay lit for a bit
the SIGHUP is never activated the node goes down and thee it sits...

I have asked on three occasiongs hee for help and my only response was check
the modems. THe modems have been checked, rechecked and double checked...
Besides the fact it worked before. I would love to continue using linux for
our system but tell ya what... The way it sits I cannot even keep the modems
alive...

Any help that is real help would be appreciated... I am getting real close to
scrapping linux. The BBS I have been expanding upon is now a fairly formidable
item... It has full chat & messaging and much more. Makes Drealms and any other
PD bbs software look fairly sad. But I must admit I am getting tired of fighting
linux every step of the way... One day it works fine, SIGHUPS are caught
the next none are caught... HELP?

I am desperate...

--Rick

 
 
 

1. Can someone mail me the uugetty DEBUG output for a Dial In ?

I have serious problems, installing uugetty (2.0.7d) for dialing in.
(I read the SERIAL.HOWTO, the mini-getty_ps.howto and all the
README files)

After making the connection, uugetty transmitts the CONNECT 2400
message and then nothing more happens.

I would like to know the DEBUG output from a working dial in
sequence. You can get such a output if you
a) starts uugetty with the -D052 option in /etc/initab or
b) adds a line with DEBUG=052 to the file /etc/conf.uugetty.ttyS?
  (probably it is in /etc/defaults on your system)

On my system the debug output is in /usr/adm/debug.

This is the debug output from my system after getting the call:
Aug 23 17:01:35 sent9 uugetty[105]: D_RUN: signal set: funcs.c:495
Aug 23 17:01:35 sent9 uugetty[105]: D_RUN: alarm set: funcs.c:496
Aug 23 17:01:36 sent9 uugetty[105]: D_RUN: alarm set: funcs.c:516
Aug 23 17:01:36 sent9 uugetty[105]: D_RUN: signal set: funcs.c:517
Aug 23 17:01:36 sent9 uugetty[105]: D_INIT: EXPECT: <30> (RING), GOT:  
^JRING -- got it
Aug 23 17:01:36 sent9 uugetty[105]: D_RUN: opening line: /dev/ttyS1
Aug 23 17:01:36 sent9 uugetty[105]: D_RUN: locking the line
Aug 23 17:01:36 sent9 uugetty[105]: D_RUN: signal set: uufuncs.c:57
Aug 23 17:01:36 sent9 uugetty[105]: D_RUN: signal set: uufuncs.c:58
Aug 23 17:01:36 sent9 uugetty[105]: D_RUN: signal set: uufuncs.c:59
Aug 23 17:01:36 sent9 uugetty[105]: D_RUN: signal set: uufuncs.c:60
Aug 23 17:01:36 sent9 uugetty[105]: D_RUN: delay(2)
Aug 23 17:01:38 sent9 uugetty[105]: D_RUN: performing connect sequence
Aug 23 17:01:38 sent9 uugetty[105]: D_INIT: chat("" ATA\r CONNECT\s\A)  
called
Aug 23 17:01:39 sent9 uugetty[105]: D_INIT: EXPECT: ([nothing])
Aug 23 17:01:39 sent9 uugetty[105]: D_INIT: SEND: (ATA^M) -- OK
Aug 23 17:01:39 sent9 uugetty[105]: D_RUN: signal set: funcs.c:495
Aug 23 17:01:39 sent9 uugetty[105]: D_RUN: alarm set: funcs.c:496
Aug 23 17:01:48 sent9 uugetty[105]: D_RUN: alarm set: funcs.c:516
Aug 23 17:01:48 sent9 uugetty[105]: D_RUN: signal set: funcs.c:517
Aug 23 17:01:48 sent9 uugetty[105]: D_INIT: EXPECT: <30> (CONNECT  
[speed]), GOT: ATA^M^M^JERROR^M^J^M^JRING^M^J^M^JCONNECT 2400^M -- got it
Aug 23 17:01:48 sent9 uugetty[105]: D_INIT: chat() successful
Aug 23 17:01:48 sent9 uugetty[105]: D_RUN: AutoRate = (2400)
Aug 23 17:01:48 sent9 uugetty[105]: D_RUN: setting speed to 2400
Aug 23 17:01:49 sent9 uugetty[105]: D_RUN: signal set: main.c:926
Aug 23 17:01:49 sent9 uugetty[105]: D_RUN: alarm set: main.c:927
Aug 23 17:01:49 sent9 uugetty[105]: D_RUN: getlogname() called

  Thanks,


2. No more HP Pavilion ZT1130

3. Want to hire someone to write me three scripts

4. trouble logging in after adding a user

5. Most Bizzare Problem with Linux I have ever encountered... someone PLEASE HELP.

6. Q: ok prompt on serial console?

7. Rant, help needed, *problems* Grrr. Plea!

8. Running X session within another Window Manager like kde

9. Athlon and/or VIA chipset problems (was: lost interrupt hell - Plea for Help)

10. Most Bizzare Problem with Linux I have ever encountered... someone PLEASE HELP.

11. Serial problems, Desperate plea for help!

12. Can someone help me with my Linux adsl gateway problem

13. Urgent plea for help on PPP Problem