Re: [HACKERS] postmaster locking issues.
От | Marc G. Fournier |
---|---|
Тема | Re: [HACKERS] postmaster locking issues. |
Дата | |
Msg-id | Pine.BSF.4.05.9810150557180.4514-100000@hub.org обсуждение исходный текст |
Ответ на | Re: [HACKERS] postmaster locking issues. (Bruce Momjian <maillist@candle.pha.pa.us>) |
Список | pgsql-hackers |
On Mon, 12 Oct 1998, Bruce Momjian wrote: > > > >> 5. The port lock will be kept in '/var/opt/pgsql/lock/'. > > > > As everyone has pointed out, we can't count on a specific convention for > > where the lock file should go. However, we can probably count on a > > convention to be followed on a particular OS. That would seem to be > > something to define in Makefile.port, which could then be overridden by > > a configure option or Makefile.custom entry. > > > > On my RedHat Linux systems, the appropriate place seems to be /var/lock > > or /var/lock/pgsql. > > I have talked to Billy. I see no real value to try chasing around > OS-specific lock file locations. /tmp is fine, and if they don't have > sticky bits in /tmp, they have much larger problems than the location of > the lock file. I personally do not like putting stuff like that into /tmp.../tmp, IMHO, is such that if i need to, I can run 'find /tmp -mtime +1 -exec rm {} \;" without feeling a twinge of worry or guilt...putting lock and/or pid files in there is just plain *wrong*... Marc G. Fournier scrappy@hub.org Systems Administrator @ hub.org scrappy@{postgresql|isc}.org ICQ#7615664
В списке pgsql-hackers по дате отправления: