Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, nicolas(at)marchildon(dot)net, Bugs for PostgreSQL <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd
Date: 2013-12-09 21:35:56
Message-ID: 27892.1386624956@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Updated patch attached, with centralized checking for errno and more
> consistent behavior for username lookups.

This bit is not good:

+ errno = 0; /* clear errno before call */
+ pw = getpwuid(geteuid());
+ if (!pw)
+ {
+ *errstr = psprintf(_("effective user id %d lookup failure: %s"),
+ (int) geteuid(), errno ? strerror(errno) :
+ _("user does not exist"));

The second call of geteuid() could clobber errno before strerror can see it.
You should compute geteuid() just once and keep it in a variable.

Also, I don't think that error message meets our style guidelines.
Maybe "failed to look up user id %d: ..." ?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2013-12-09 21:45:39 Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd
Previous Message Bruce Momjian 2013-12-09 21:05:32 Re: BUG #8139: initdb: Misleading error message when current user not in /etc/passwd