Re: Can't not run initdb - Mailing list pgsql-cygwin

From Mike G
Subject Re: Can't not run initdb
Date
Msg-id 1104384896.19080.2.camel@localhost.localdomain
Whole thread Raw
In response to Can't not run initdb  (Tan Phat Huynh <tanphat99ct@yahoo.com>)
List pgsql-cygwin
Cygserver is not running and / or not in your path.

That is what causes sig 11.

See the readme included with the install.

On Tue, 2004-12-28 at 06:21, Tan Phat Huynh wrote:
> Hi all.
> My name: Tan Phat
> My Email: tanphat99ct@yahoo.com
> Postgresql version : Postgresql-7.4.5
>
> My problem:
> I can't not run initdb
> Please help me sovle this problem
>
> $ initdb -D /usr/local/pgsql/data -W -E LATIN1
> The files belonging to this database system will be
> owned by user "staff2".
> This user must also own the server process.
>
> The database cluster will be initialized with locale
> C.
>
> creating directory /usr/local/pgsql/data... ok
> creating directory /usr/local/pgsql/data/base... ok
> creating directory /usr/local/pgsql/data/global... ok
> creating directory /usr/local/pgsql/data/pg_xlog... ok
> creating directory /usr/local/pgsql/data/pg_clog... ok
> selecting default max_connections... Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> 10
> selecting default shared_buffers... Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> Signal 12
> 50
> creating configuration files... ok
> creating template1 database in
> /usr/local/pgsql/data/base/1... Signal 12
>
> initdb: failed
> initdb: removing data directory
> "/usr/local/pgsql/data"
>
>
>
>
> __________________________________
> Do you Yahoo!?
> The all-new My Yahoo! - What will yours do?
> http://my.yahoo.com
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org

pgsql-cygwin by date:

Previous
From: Tan Phat Huynh
Date:
Subject: Can't not run initdb
Next
From: "roblam"
Date:
Subject: Re: pgsql 8.0 on win2000 server error 2203