Re: Starting postmaster at boot - Mailing list pgsql-general
From | Adam Lang |
---|---|
Subject | Re: Starting postmaster at boot |
Date | |
Msg-id | 026401c01e8c$78b8b700$330a0a0a@Adam Whole thread Raw |
In response to | Re: Starting postmaster at boot (David Veatch <dveatch@sunflower.com>) |
Responses |
Re[2]: Starting postmaster at boot
|
List | pgsql-general |
OH! I get it. Whereas I have the environment variables in postgres's .bash_profile, you have it set where those variables are loaded for all users, correct? But the part that I don't get is that (typing it at console) I can start postgresql (while logged in as postgres) with the command: postmaster -i because I have the variables for the location of postmaster and pgdata set. But, I would assume that typing the absolute paths would have gotten around that for when I was doing the su. Are there other environment variables I didn't take insto consideration? Adam Lang Systems Engineer Rutgers Casualty Insurance Company ----- Original Message ----- From: "Mitch Vincent" <mitch@venux.net> To: "Adam Lang" <aalang@rutgersinsurance.com> Cc: "PGSQL General" <pgsql-general@postgresql.org> Sent: Thursday, September 14, 2000 4:40 PM Subject: Re: [GENERAL] Starting postmaster at boot > The reason I didn't have to use the -l is that I have everything PostgreSQL > needs (as far as environment variables) already set, because this machine is > a dedicated PostgreSQL server. > > Sorry, should have thought about that before I replied but it seems you have > it running now, that's great.. Good luck! > > -Mitch > > ----- Original Message ----- > From: "Dale Walker" <dale@icr.com.au> > To: "Adam Lang" <aalang@rutgersinsurance.com> > Cc: "PGSQL General" <pgsql-general@postgresql.org> > Sent: Thursday, September 14, 2000 1:33 PM > Subject: Re: [GENERAL] Starting postmaster at boot > > > > Adam Lang wrote: > > > > > > I didn't directly use your method, but you nonetheless solved my > problem. > > > >From the beginning everyone was telling me to put this into my > rc.local: > > > su postgres -c "/usr/local/pgsql/bin/postmaster -D > /usr/local/pgsql/data -i > > > /usr/local/pgsql/postgres.log 2>&1 &" > > > > > > It was never working. I noticed you had a tag "-l" in yours for su. I > > > looked up the reason for it and gave it a try. So the script: > > > su -l postgres -c "/usr/local/pgsql/bin/postmaster -D > > > /usr/local/pgsql/data -i /home/postgres/postgres.log 2>1 &" > > > does work. > > > > > > I still don't understand the point of the 1's and 2's in the command > though. > > > > > > it's a method for redirecting STDERR --> STDOUT > > > > this is especially usefull in scripts > > > > normally I use [scriptname >/dev/null 2>&1] to send any unwanted output > > to /dev/null > > > > > > > > Why is everyone else's script working without the -l and mine wasn't? > > > > > > > > > '-l' uses the login profile for the su'd user... this is similar to a > > 'simuated login', without it , it was only referencing variables from > > your roo profile ... (ie. no PGDATA,etc..) > > > > > > -- > > Dale Walker dale@icr.com.au > > Independent Computer Retailers (ICR) http://www.icr.com.au > > ICRnet http://www.icr.net.au > >
pgsql-general by date: