Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] postmaster crash and .s.pgsql file

From: Brook Milligan <brook(at)trillium(dot)NMSU(dot)Edu>
To: maillist(at)candle(dot)pha(dot)pa(dot)us
Cc: hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] postmaster crash and .s.pgsql file
Date: 1998-01-29 19:10:14
Message-ID: 199801291910.MAA25411@trillium.nmsu.edu (view raw or flat)
Thread:
Lists: pgsql-hackers
> No.  Make /var/run writable by some group (e.g., group pidlog) and put
> postgres (and other things like root or daemon or ..., whatever needs
> to log pid files) in that group.

   We can't expect the user to be able to change /var/run permissions. 
   Must be in pgsql/ or /tmp.

No, "normal" users shouldn't be allowed to do so, obviously.  But, are
there real systems in which a database maintainer (i.e., user
postgres) cannot cooperate with the system admin (i.e., user root) to
accomplish this?  In practice, is it really envisioned that postgres
should be _so_ distinct from the system?  For example, don't most
people run the postmaster from the system startup scripts, and isn't
that the same thing?  How did those commands get inserted into the
startup scripts if not by root?

Cheers,
Brook

In response to

Responses

pgsql-hackers by date

Next:From: The Hermit HackerDate: 1998-01-29 20:10:15
Subject: Re: [HACKERS] postmaster crash and .s.pgsql file
Previous:From: Bruce MomjianDate: 1998-01-29 19:04:32
Subject: Re: [HACKERS] Error in nodes/parse_node.h

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group