| From: | "Thomas G(dot) Lockhart" <lockhart(at)alumni(dot)caltech(dot)edu> |
|---|---|
| To: | "Marc G(dot) Fournier" <scrappy(at)hub(dot)org> |
| Cc: | "Billy G(dot) Allie" <Bill(dot)Allie(at)mug(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Taral <taral(at)mail(dot)utexas(dot)edu>, hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] postmaster locking issues. |
| Date: | 1998-10-15 14:34:43 |
| Message-ID: | 36260803.4FA19246@alumni.caltech.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > On my RedHat Linux systems, the appropriate place seems to be
> > /var/lock or /var/lock/pgsql.
> FreeBSD has a /var/spool/lock...Solaris has /var/spool/locks
> we could put it into the template for the OS as a -DLOCK_DIR="", which
> would probably be the simplist (instead of having configure searching
> all possibilities)...
I like this. And one can override it with Makefile.custom if desired.
There are other items appearing in some of the Makefiles which would do
better to go in the templates. In particular, some of the library
Makefiles have big chunks of "ifeq ($(PORTNAME), xxx)" code containing
lots of duplicate or repetative info. We can/should move all of this
stuff out into the templates and into configure.
Something to do for v6.5...
- Tom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Brook Milligan | 1998-10-15 14:48:45 | Re: [PATCHES] TCL/TK configuration clean-up patches |
| Previous Message | Marc G. Fournier | 1998-10-15 14:34:27 | Re: [HACKERS] PostgreSQL v6.4 BETA2... |