From: | Tim Holloway <mtsinc(at)southeast(dot)net> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-hackers(at)hub(dot)org |
Subject: | Re: [HACKERS] pid file for postmaster? |
Date: | 1999-11-25 13:19:45 |
Message-ID: | 383D3771.E0282D5B@southeast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Red Hat ALREADY creates a file "postmaster.pid" in the /var/lock directory.
I don't know how far the /var/lock convention goes across different platforms,
but I recommend using IT or its equivalent, I still have scars from my OS/2
days where every product put its goodies in a different place and you had to
guess where, how, and in what format.
Regards,
Tim Holloway
Tatsuo Ishii wrote:
>
> From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
> > Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> writes:
> > > It would be nice if postmaster has its own pid file to send signals to
> > > it. I think the pid file could be placed under $PGDATA. Opinions?
> >
> > Yes, that's been discussed before, and I think it's even got an entry
> > on the TODO list. If you've got time to tackle it now, great!
> >
> > $PGDATA seems like the right place to put the file, since we can only
> > have one active postmaster at a time in a database directory.
>
> Right.
>
> > I assume you'll also create a script that sends SIGTERM or other
> > requested signal to the postmaster, using this file?
>
> Of course:-) I'm thinking about to make an apachectl-like script.
> --
> Tatsuo Ishii
>
> ************
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak - Zakkr | 1999-11-25 13:43:20 | PgAccess - small bug? |
Previous Message | Peter Eisentraut | 1999-11-25 13:08:41 | Re: [PATCHES] ':' and ';' operators |