Hi Glen,
How annoying :-(. I think what you need to do is use truss or strace
or local equivalent with the follow-forks flag, so that you can see what
the stand-alone backend process does, not just initdb itself.
Ok, next round. I just have truss as an option, because strace didn't
work at my AMD64. Hope its helpfull:
$ truss -f -o /tmp/pgtuss-f.txt /usr/local/pgsql/bin/initdb -D
/usr/local/pgsql/data
Result:
http://www.dddbl.de/pg-truss-f.txt
[ scratches head ... ] That looks like it got interrupted before
getting to anything interesting. Did the console printout show any "Bad
system call" reports?
I didn't see it mentioned earlier in this thread - is
security.jail.sysvipc_allowed=1? This will automatically be set to 1 if
you have jail_sysvipc_allow="YES" in rc.conf.
Yes, it is:
# sysctl -a | grep sysvipc_allowed
security.jail.sysvipc_allowed: 1
Greetings,
Torsten
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
