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@sss.pgh.pa.us> wrote:
> Michael Felt <mamfelt@gmail.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
>
