From: NU013809@NDSUVM1.BITNET (Greg Wettstein) Subject: Re: UUCP size ok now, but dumps core... :( Date: 17 Mar 1993 11:29:18 GMT
> Tim Foley (tfoley@camaro.uucp) wrote:
> : Ok, the size problem was the -g option (gdb) but with or without the
> : -fwritable-strings option, uucico seg faults.
> :
> : Is there any mods to make uucp 1.04 with with 0.99p6 / gcc2.3.3 /libc4.2?
>
> Perhaps libc4.2 is the problem? I compieled uucp1.04 a couple of days ago
> *without* any patches and it runs fine - I'm polling my news with uucico
> two times a day. I didn't even need the -fwritable-strings.
>
> My setup: .99pl6, gcc2.3.3, libc4.3 (all from the latest SLS release)
I can support the notion that Taylor-1.04 compiles straight out of the
box. We have been running it with 0.99PL(6,7) compiled with GCC 2.3.3 and
have had success with both the 4.2 and 4.3PL2 libraries. I would say that
we have averaged 75-100 connects per day for two weeks with not problems.
There is a subtle modification that may cause trouble under Linux however.
We discovered that a normal chat sequence functions properly but a chat
sequence specified from a dailer script (dial file) fails to work as it
should. Specifically random characters will be dropped from the send
string.
This problem is due to a 'settling' problem in a function called
fsysdep_modem_begin_dial in the file serial.c in the unix subdirectory.
This function is responsible for turning on CLOCAL mode before a chat
script begins. On line 1669 (approx.) there is a call to the macro
fsetterminfo to turn on CLOCAL mode. Evidently the Linux serial drivers
need some time to 'settle' after being opened before they will respond
properly to an ioctl. Inserting a sleep(2) just before the fsetterminfo
call seems to reestablish consistent behavior.
Note that CLOCAL mode is turned off (after the chat script completes) by
a call to fsetterminfo around line 1628. I dropped in a sleep(2) just
before this call to be on the safe side.
I dropped a note to Ian so he knows about it, in fact he is the one that
told me where to start looking. Otherwise 1.04 has been a real pleasure to
work with.
Archaelogical note:
I almost hated to start monkeying with 1.04. When our research group
first brought up UUCP under Linux it was in the 0.95 territory. There
were fairly massive problems with the serial drivers at that point. I
remember one all-nighter that I sat crouched with a logic analyzer and
a 'scope trying to figure out where the serial stream was getting
corrupted. This was after compiling Taylor about 250 times with
various and sundry configuration options.
Interestingly the serial problems also manifested themselves by BASH
refusing to transmit a linefeed after a command was type in. Subsequent
output lines were fine but the first line of output always overwrite
the command line. Aw the good 'ol days....
As always,
Dr. G.W. Wettstein
Oncology Research Division Computing Facility
Fargo Clinic / MeritCare
UUCP: uunet!plains!wind!greg
INTERNET: greg%wind.uucp@plains.nodak.edu
Phone: 701-234-2833
`The truest mark of a man's wisdom is his ability to listen to other
men expound their wisdom.'