On Tue, 14 Dec 2010, Wallace Roberts Consulting wrote:
It may or may not be necessary, but I would do it just to make sure there are no collisions between the new version & the older version. For example, if the older version is still running during the upgrade, it might write into a file or database table created by upgrade. That would be, as Kernighan & Ritchie once wrote, a ghastly error.
I'm the only user, and I don't have l123 displaying in a firefox tab when I upgrade the scripts. It turns out that I did have an old copy of libpq.so from the upgrade from postgres-8.3.3 in /var/lib/pgsql (where the slackbuilds.org puts 'em) to -9.0.1 in /usr/local/pgsql (where the default postgres 'make install' puts 'em). For some reason yet to be determined by the SlackBuild script developer, it will not build here without errors despite running the most current distribution. Restarting httpd made it happy despite the server not being used when I did the upgrade. Computers may be logical but they're not always rational. Thanks, Wallace, Rich _______________________________________________ SQL-Ledger mailing list [email protected] http://lists.ledger123.com/mailman/listinfo/sql-ledger
