Re: [HACKERS] flock patch breaks things here
От | The Hermit Hacker |
---|---|
Тема | Re: [HACKERS] flock patch breaks things here |
Дата | |
Msg-id | Pine.BSF.4.05.9810292207190.28793-100000@thelab.hub.org обсуждение исходный текст |
Ответ на | Re: [HACKERS] flock patch breaks things here (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] flock patch breaks things here
|
Список | pgsql-hackers |
On Sun, 30 Aug 1998, Tom Lane wrote: > The Hermit Hacker <scrappy@hub.org> writes: > > either way, moving the pid file (or > > socket, for that matter) from /tmp should be listed as a security related > > requirement for v6.4 :) > > Huh? There is no pid file being generated in /tmp (or anywhere else) > at the moment. If we do add one, it should not go into /tmp for the > reasons I gave before. > > Where the Unix-domain socket file lives is an entirely separate issue. > > If we move the socket out of /tmp then we have just kicked away all the > work we did to preserve backwards compatibility of the FE/BE protocol > with existing clients. Being able to talk to a 1.0 client isn't much > good if you aren't listening where he's going to try to contact you. > So I think I have to vote in favor of leaving the socket where it is. Let me put my vote in...: $PGSQLHOME/run/{pgsql.pid,pgsql.pid.socket} Screw backwards compatibility...v6.5 becomes v7.0 *shrug* Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org
В списке pgsql-hackers по дате отправления: