|
From: <ja...@op...> - 2001-06-16 00:32:30
|
"Jason E. Stewart" <ja...@op...> writes: > "Joe Roden" <ro...@ai...> writes: > > > > Can you reconfigure GeneX to *not* use tcp/ip to connect with the DB, > > > and give that a try. > > > > Will do, and that may well do the trick. That sounds like the sort of > > tweak that could cause the problem. > > Heh. > > Actually you *can't* configure genex to use tcp/ip sockets. No matter > what you tell it to use, the installation script forces communication > with a local Pg server :-( I know this must be the problem, because their was a typo in Genex.pm that prevented the use of a port number. So you must have been using Unix domain sockets to talk to the wrong DB all along. Ok. Fix is now checked into CVS. To get it do the following: $ cvs -d :pserver:ano...@ge...:/home/cvsroot/opengenex login (Logging in to ano...@ge...) CVS password: [no password, just hit enter] $ cvs -z3 -d :pserver:ano...@ge...:/home/cvsroot/opengenex \ co -r Rel-1_0_1-branch genex-server When you run install-all.pl, you will need to tell it that you are doing an update ([U] instead of [N]), and then tell it what the root of your previous installation was. Then go into prompting mode and specify the values for Host and Port that you *intended* to use all along. Let me know how it goes. jas. PS. If you don't want to get it from CVS for any reason, let me know and Harry or I will cut a new release this weekend. But be nice, I've got an OMG deadline on Monday, and a paper deadline the following Monday. So only ask *two* miracles from me ... ;-) |