Subject: Pine on SCO used wrong date

From: [email-masked] (Steve Miller)
Date: 8 Aug 1994 19:12:28 GMT

When I send mail using pine on SCO Rel 3.2 Ver 4.2 it sends the wrong date.
The date is always February 23, 1970.

On another system running SCO Unix Rel 3.2 Ver 2.0 pine aborts when trying
to start it up. 

Anyone experienced these problems before?

I have had pine running on a different system with SCO ODT 3.0
(same as SCO Unix 3.2 Ver 4.2) for months and it works just fine.
The ones with the date problem are all fresh installs on new
machines.

--
Steve Miller
[email-masked]

---

From: [email-masked] (Gunther Anderson)
Date: Mon, 15 Aug 1994 17:07:44 GMT

Steve Miller ([email-masked]) wrote:
: When I send mail using pine on SCO Rel 3.2 Ver 4.2 it sends the wrong date.
: The date is always February 23, 1970.

That's my port, and I'm running 3.2v4.2 here.  I can't say what's up with 
the date.  The system date is OK, right?

: On another system running SCO Unix Rel 3.2 Ver 2.0 pine aborts when trying
: to start it up. 

: Anyone experienced these problems before?

Someone once mentioned that to me.  Do you remember what the error was?  
In a sense, though, this isn't an ODT port, so some problem are possible 
if I inadvertantly used any non-ODT functions.  Or, if you don't mean 
ODT, and this is really a 2.0 version, ye gods, that's old.  I had this 
built with the latest TCP/IP and development system.  Who knows what 
might have changed since then.

: I have had pine running on a different system with SCO ODT 3.0
: (same as SCO Unix 3.2 Ver 4.2) for months and it works just fine.
: The ones with the date problem are all fresh installs on new
: machines.

Well, I haven't seen anything here.  Try writing some small programs to 
check the system date and time from C, and see what you get.  It's always 
possible that Pine is just reflecting a symptom of a larger problem.

Gunther Anderson

---

From: [email-masked] (Kent Hamilton)
Date: 20 Aug 1994 00:28:34 -0500

In article <[email-masked]>,
>the date.  The system date is OK, right?

Make sure you have a TZ variable in your environment.  I've seen some
flakey things happen on SCO if you don't.

>might have changed since then.

Uhhh, the networking libraries are totally different between v2.0t
and v4.x like there is no libnsl_s.a in 2.0 so if you linked Pine 
using that on a newer system then forget it.  I'm not sure what's
going to happen if you try an lstat() (Does pine use it? I didn't
look at the source.) on a 2.0 system but a core dump would be my bet.
Same thing applies to several other library changes.  I'd guess you'd
be hard pressed to get it working on 2.0 without re-writing the port.
I have to maintain both 4.x and 2.0 systems and I'm to the point I
actually have a -DSCO324 or -DSCO322 defined in the gcc spec file
for the various systems....  <yech!>
-- 
  Kent Hamilton                 |    Home:  [email-masked]
  Senior Systems Administrator  |    Work:  [email-masked]
  SCS/Compute, Inc.             |   Phone:  (314) 997-7766 ext 3070