[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: 19991214: NLDN Y2K IDD header discussion (cont.)

david,

NLDN y2k compliance testing has completed and is now correct.

NLDN ldm product queues use now 4 digit years in the new nldnldm executable.  i 
suggest
you copy this executable into place (i.e. sudo cp 
/home/nldntest/nldn.new/nldnldm
/striker1/ingest/bin) and restart the nldnldm when you bring your systems back 
up on jan
1 or 3, 2000.  (this will give people a few days to change their pqact.conf 
files.)  you
probably want all new executables (i tested with the new ones), so you might 
copy other
files too.  i.e. /home/nldntest/ingest.new/srcg++/ingest4.1.3

read /home/nldntest/README.ingest for details.
revised code for ingest4.1.3 is in /home/nldntest/ingest.new/srcg++
actually, there aren't any revisions, either to get it to compile or to make it 
y2k
compliant.  so it's the same code that is stored in /home/nldntest/ingest.tar 
except
this tarball also contains a ingest/src directory which is all trash (since the 
source
is in ingest/srcg++ in the tarball).

read /home/nldntest/README.nldn for details.
revised code for nldnldm is in /home/nldntest/nldn.new
there are a few revisions to get it to compile, and one revision to make it y2k
compliant (4 digit year instead of 2 digit year.)
should you loose track of this directory, old code is stored in
/home/nldntest/nldnldm.tar and a patchfile containing the changes is
/home/nldntest/nldnldm.y2k.patch

-sandy

p.s.  i've removed all temporary files from y2ktest.atmos.albany.edu and 
restored the
date with
ntpdate redwood.



"David J. Knight" wrote:

> Sandy,
>     that is great. thanks. I'll see what we can do about
> setting up a machine for you this afternoon.
> Before you leave town please tell us where the (revised)
> code is and how to compile it, so we can make
> it operational before the new year. I assume
> you guys are still going to announce the change?
>
> Thanks again - stay tuned.
>
> David
>
> >
> > all the executables compiled and ran fine.  they appear to be fine for jan 
> > 1.  the
> > current plan is to move to 4 digits per year in file names (and product 
> > queue
> > names)
> >
> > as far as testing goes (changing the system date to after y2k) if it 
> > doesn't happen
> > today or wed, it probably won't happen at all since i'm going to be out of 
> > town all
> > next week.
> >
> > -sandy
> >
> >
> >
> > "David J. Knight" wrote:
> >
> > > Sandy,
> > >      Oops! That is what I get for installing a
> > > compiler that I don't use (course these days
> > > you cannot install gcc without also getting g++,
> > > though without its libraries - go figure, so
> > > perhaps I can be partially excused)
> > > Perhaps that is part of the reason I had
> > > problems getting the package to compile ?-)
> > >
> > > You should be all set now. The readme suggests
> > > that libg++ is obsolete and no longer supported,
> > > but I installed it for you anyway along with stdc++
> > > (both in /usr/local/lib)
> > >
> > > Since I don't use c++ I couldn't easily test it
> > > (except for make check) so let me know if
> > > you have problems or not.
> > >
> > > Thanks
> > > david
> > > > Hi David,
> > > >
> > > > In order to compile the NLDN ingest program on aspen.atmos.albany.edu 
> > > > (or
> > > > anywhere else for that matter) using gcc2.8.1, I need libstdc++-2.8.1.1 
> > > > and
> > > > libg++-2.8.1.1a installed.  I'd do it myself and save you the trouble, 
> > > > but, of
> > > > course, this requires root access.
> > > >
> > > > thanks,
> > > > sandy
> > > >
> > > >
> > > >
> >