> > My problems with a fresh CVSup'd source went away when I ran
> > ldconfig. The name of the shared library has changed. One of the
> > symptoms is that I got an "atoi" error partway through initdb.
> I did get atoi errors for a while aswell, but apparently that was
> another problem in the source, not ldconfig. You see, before the atoi
> errors, I was getting some weird script errors in initdb itself, which
> were fixed by ldconfig.
Yes, I saw those too, and I think it was a missing result from pg_id
which did it. Wasn't graceful and we should fix it before the v6.4
release, otherwise many new installations will have the same trouble.
The script should check for a non-empty UID and barf or prompt for it
otherwise. Is anyone actively working on it? Don't remember who
submitted the original patches but it would be nice if they would stick
with it and toughen it up a bit. Otherwise perhaps we should revert to
the original version. Like the features though...
- Tom