Just swinging by and I have a small bit of time for comment and some hopefully
useful information.
Windows and a GUI would not make any difference to this problem. The issue is that it is an unmaintained
project. Windows has lots of similar problems with unmaintained software - for example: old stuff that simply
will not not run on Win7/8 anymore. Not much keeps working indefinitely without any maintenance. I am actually
surprised that MOSS has run so long and so well with not much maintenance.
In any case, every once in a while I fire up the MOSS and play the Uru for nostalgia, since it is easy and speedy and
I do not have to worry about downloading stuff, accounts, nor worry about client changes. I am running a Debian box
and PgSQL 9.1, so can give data on this setup. It has been a while since I set this up, so hopefully I am remembering
the pain points I hit.
First difference that you have already noticed is that pg now defaults to "peer" auth for local sockets in
pg_hba.conf. We can use "trust" as rarified has recommended, but that allows any user at all on the machine
to access the socket, which bothers me personally. I used md5, because at least a password is required for that.
It is merely a matter of preference, since MOSS is not often run on a true multi-tenant box.
I see you already have a "moss" user created for the db, so to create the DB easily, log into your box as root and do
a "su postgres" or "su postgresql" (does not matter which one your system uses - we just want to be db admin), fire up
psql and do this command:
Code: Select all
CREATE DATABASE moss WITH ENCODING='UTF8' LC_CTYPE='en_US.UTF-8' LC_COLLATE='en_US.UTF-8' OWNER=moss TEMPLATE=template0 CONNECTION LIMIT=-1;
That will set up your DB with the right owner with no hassle or encoding warnings. I do not have UTF as a locale, so the
above was the only way I could set it up without psql complaining about my system locale.
You also need to load the extension differently in 9.1, but I see that there is another thread where someone
already put the details on how to do that, so you are good there.
rarified has the correct answer for the UTF error on the SDL manager import. You need to set
"standard_conforming_strings = off". The problem is that with it on, the "\" is treated literally,
and the old formatted escapes that MOSS uses break. I set the "standard_conforming_strings = off" in the
postgresql.conf file, and have not noticed any problems with other apps.
I would recommend changing the above setting before running in the "moss.sql" file. I do not recall if there are
any old-style escapes in that file that would be a problem, but it is best to have it all set properly before importing data.
Well, that is all I have. Hope it might help a little bit.