Re: Re: Sure enough, the lock file is gone
| От | The Hermit Hacker |
|---|---|
| Тема | Re: Re: Sure enough, the lock file is gone |
| Дата | |
| Msg-id | Pine.BSF.4.31.0101282137070.9459-100000@thelab.hub.org обсуждение исходный текст |
| Ответ на | Re: Re: Sure enough, the lock file is gone (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: Re: Sure enough, the lock file is gone
|
| Список | pgsql-hackers |
On Sun, 28 Jan 2001, Tom Lane wrote: > "Oliver Elphick" <olly@lfix.co.uk> writes: > > No, UNIX sockets are specifically mentioned as belonging under /var/run. > > In section 5.10 "/var/run : Run-time variable data", it says: "Programs > > that maintain transient UNIX-domain sockets should place them in this > > directory." > > > So what ever the outcome for the wider PostgreSQL community, I must make > > the change to conform to Debian policy. > > Just out of curiosity, does Debian enforce a nonstandard location for > X sockets as well? Just curious here ... there seems to have been *alot* of energy expended on this ... is there any reason why we don't just have a configuration option like other software has, that defaults to /tmp like we have it now, but that makes it easier for others to change it for their installs, as required?
В списке pgsql-hackers по дате отправления: