Skip site navigation (1) Skip section navigation (2)

Re: BUG #5267: initdb fails on AIX: could not identify current directory

From: Michael Felt <mamfelt(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5267: initdb fails on AIX: could not identify current directory
Date: 2010-01-07 14:41:53
Message-ID: 9ade2d511001070641m4d7b1d8ew40e6e2ae19340f8d@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Well, there is an argument that a system call is using to get somewhere?
Even if it is a number, it is something. I could do an ncheck or whatever to
at least find what it is calling.

As I am not at all familiar with the code - just give me source to debug,
and I'll work from that.

On Thu, Jan 7, 2010 at 3:35 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Michael Felt <mamfelt(at)gmail(dot)com> writes:
> > I suppose I could turn on audit and see if it is trying to access a hard
> > coded directory. But, in any case, I would update the error message to at
> > least mention the directory name it is having issues with.
>
> Well, the problem is what to print?  The failure we are trying to report
> is exactly that we *can't get* the name of the directory.
>
>                        regards, tom lane
>

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2010-01-07 14:57:15
Subject: Re: BUG #5267: initdb fails on AIX: could not identify current directory
Previous:From: Tom LaneDate: 2010-01-07 14:35:52
Subject: Re: BUG #5267: initdb fails on AIX: could not identify current directory

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group