Rich Shepard <[EMAIL PROTECTED]> writes:
> On Thu, 26 Jan 2006, Joshua D. Drake wrote:
>
>> Although I am glad you were able to get up and running, typically you don't
>> want to "move" libs like that. Instead update your /etc/ld.so.conf and run
>> ldconfig.
>
>True, Josh. What I'd prefer to d
On Thu, 26 Jan 2006, Joshua D. Drake wrote:
Although I am glad you were able to get up and running, typically you don't
want to "move" libs like that. Instead update your /etc/ld.so.conf and run
ldconfig.
True, Josh. What I'd prefer to do is remove /usr/local/pgsql/ once I know
that nothing
Here, it was the move from /usr/local/pgsql to /var/lib/pgsql that caused
me all this grief.
A huge "thank you" to all of you -- and especially Jim.
Although I am glad you were able to get up and running, typically you
don't want to "move" libs like that. Instead update your /etc/ld.so.c
On Thu, 26 Jan 2006, Rich Shepard wrote:
What do I do to trace the source of this problem and fix it?
Thanks to Jim I found that libpq.so.3 were in the old directory. As soon as
I moved them to /usr/lib (with libpq.so.4), SQL-Ledger allowed me to log in.
All of this reminds me of the tim
