Re: initdb problem

From: "Phillip Smith" <phillip(dot)smith(at)weatherbeeta(dot)com(dot)au>
To: "'Joe Barwell'" <jbar(at)es(dot)co(dot)nz>, <pgsql-admin(at)postgresql(dot)org>
Subject: Re: initdb problem
Date: 2007-06-21 01:32:01
Message-ID: 007501c7b3a3$f7b899e0$9b0014ac@wbaus090
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

My bad - is has the shell, but as you say, the home directory is /dev/null

NOW, I must preface this with a warning saying that I have NOT tested this,
and do not guarantee that it will work. I found it on a Mac forum and have
never tried it, or seen confirmation that it will work. Follow on at your
own risk!

Apparently Mac stores all it's user info in something called Net Info (not
/etc/passwd unless in Single User Mode). To change the home directory of a
user (as best I can tell), you would need to execute this at a terminal
prompt:

niutil -destroyval -u admin . /users/postgres home /dev/null
niutil -appendprop -u admin . /users/postgres home /Library/postgreSQL8

Once again, use at your own risk! Do let us know if it worked or not.

Cheers,
~p

*******************Confidentiality and Privilege Notice*******************

The material contained in this message is privileged and confidential to
the addressee. If you are not the addressee indicated in this message or
responsible for delivery of the message to such person, you may not copy
or deliver this message to anyone, and you should destroy it and kindly
notify the sender by reply email.

Information in this message that does not relate to the official business
of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta.
Weatherbeeta, its employees, contractors or associates shall not be liable
for direct, indirect or consequential loss arising from transmission of this
message or any attachments

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Joe Barwell 2007-06-21 04:49:58 Re: initdb problem
Previous Message Joe Barwell 2007-06-21 00:58:22 Re: initdb problem