Re: stderr & win32 admin check
От | Dave Page |
---|---|
Тема | Re: stderr & win32 admin check |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E4A989@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | stderr & win32 admin check ("Magnus Hagander" <mha@sollentuna.net>) |
Ответы |
Re: stderr & win32 admin check
Re: stderr & win32 admin check Re: stderr & win32 admin check |
Список | pgsql-patches |
> -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > Sent: 15 June 2004 14:58 > To: Magnus Hagander > Cc: Dave Page; pgsql-patches@postgresql.org > Subject: Re: [PATCHES] stderr & win32 admin check > > "Magnus Hagander" <mha@sollentuna.net> writes: > >> "Can't run Postgres securely" would be a > more-than-sufficient reason > >> not to support NT4, IMHO. > > > It could still be run on NT4 under the following conditions: > > 1) Running as a service > > 2) Running if the user logged in is not an administrator. > > Well, isn't "running as a service" sufficient? I thought > that was the only interesting case for non-hackers anyway. > > As long as you get an error message that's reasonably clear > about what you can do instead, this hardly seems like a showstopper... Well, that's kinda the point. If you are a hacker who has local admin privs (not exactly unusual on Windows networks - in some cases Power User group membership is required to run legacy software), you *cannot* run PostgreSQL except as a service, thus potentially making it a show stopper for those users. Personally I don't care as I use XP/2K3 anyway, but having been told my autovacuum service code needed to support NT4.... Regards, Dave
В списке pgsql-patches по дате отправления: