[blfs-dev] postgresql, and policy

Ken Moffat zarniwhoop at ntlworld.com
Thu Sep 12 13:36:01 PDT 2013

On Thu, Sep 12, 2013 at 03:04:57PM -0500, Bruce Dubbs wrote:
> Now proceed as a normal user (note different sed):
> sed -i -e '/DEFAULT_PGSOCKET_DIR/s at tmp@run/postgresql@' \
>      src/include/pg_config_manual.h &&
 Different construction of the sed, but same result : from my
bash_history -
  713  rm -rf postgresql-9.3.0
  714  cp -a postgresql-9.3.0.{orig/,current}
  715  cp -a postgresql-9.3.0.{orig/,new-sed}
  716  cd postgresql-9.3.0.current/
\"/run/postgresql\"@"     -i src/include/pg_config_manual.h
  718  cd ../
  719  cd postgresql-9.3.0.new-sed/
  720  sed -i -e '/DEFAULT_PGSOCKET_DIR/s at tmp@run/postgresql@'
  721  cd ..
  722  diff -Naur postgresql-9.3.0.current/
  723  history

 And the result from !722 is:
ken at jtm1 /scratch/ken $!722
diff -Naur postgresql-9.3.0.current/ postgresql-9.3.0.new-sed/
ken at jtm1 /scratch/ken $

 Checking, this has to be a single directory so attempting to
use /run/postgresql followed by /tmp is not supported - using a
different directory means patching the user (the regress test) to
pass it.

 As I said, your earlier version works for you but not for me -
details in the ticket, I don't profess to understand that problem.

das eine Mal als Tragödie, dieses Mal als Farce

More information about the blfs-dev mailing list