tderr on the terminal.
"$po_path" ${1+"$@"} &1 &
fi
# if had an old lockfile, check to see if we were able to start
if [ -n "$oldpid" ];then
sleep 1
if [ -f "$PIDFILE" ];then
if [ "`sed -n 1p $PIDFILE`" = &
t;$PIDFILE" ];then
if [ "`sed -n 1p $PIDFILE`" = "$oldpid" ];then
echo "$CMDNAME: cannot start postmaster" 1>&2
echo "Examine the log output." 1>&2
exit 1
fi
fi
fi
# wait for postmaster to start
if [ "$wait&q
, BEFORE you exit, do this:
1) ps
This gives you a list of active processes.
2) Find the pid for postgres who's ppid is 1.
3) kill -15 that pid.
4) Wait for the message that the database is shut down.
Now you can exit.
______
J
d this problem do this:
1) ps
This gives you a list of active processes.
2) Find the pid for Postgres who's ppid is 1.
3) kill -15 that pid.
4) Wait for the message that the database is shut down.
You are now shut down.
______
J
" it works just fine.
______
John Pagakis
Email: [EMAIL PROTECTED]
"If enlightenment is not where you are standing,
where will you look?"
-- Zen saying
This signature generated by
... and I Quote!!(tm) Copyrig
02e-1
uw-imap-util2002e-1
vim 6.2-3
w32api 2.4-1
wget1.8.2-2
which 1.5-2
whois 4.6.2-1
WindowMaker 0.80.0-2
wtf 0.0.4-4
x2x 1.27-2
Xaw3d 1.5-1
xerces-c2.3.0-2
s Postgres down.
Why would the interpreter rejecting the command line for kill when it
appears to be well formed?
Any help would be greatly appreciated.
__
John Pagakis
Email: [EMAIL PROTECTED]
"Ideas are more powerful than
7 matches
Mail list logo
