On Sat, Dec 15, 2012 at 09:02:34AM -0600, David Noel wrote:
> Ahh... the security.bsd. sysctl output had the answer: I had
> security.bsd.hardlink_check_gid and security.bsd.hardlink_check_uid
> set to 1 in sysctl.conf. Removing that fixed the problem.
Then, why did you set it ?
The sysctl indeed
Ahh... the security.bsd. sysctl output had the answer: I had
security.bsd.hardlink_check_gid and security.bsd.hardlink_check_uid
set to 1 in sysctl.conf. Removing that fixed the problem.
Many thanks,
-David
> Show the ktrace from the same error on UFS.
5179 postgres CALL unlink(0x7fffe
On Fri, Dec 14, 2012 at 10:43:00PM -0600, David Noel wrote:
> I've been fighting with a bug I can't quite seem to figure out and was
> told that this might be the place to come. I'm running
> postgresql-9.2.2 on FreeBSD 8.3-RELEASE-p5 and am having things break
> down when I try to run initdb. I go
I've been fighting with a bug I can't quite seem to figure out and was
told that this might be the place to come. I'm running
postgresql-9.2.2 on FreeBSD 8.3-RELEASE-p5 and am having things break
down when I try to run initdb. I got in contact with the pgsql-general
mailing list and we debugged the
I just compiled a generic kernel and tried it again.. same error. So
no funny business going on with my kernel settings it seems.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send a
I've been fighting with a bug I can't quite seem to figure out and was
told that this might be the place to come. I'm running
postgresql-9.2.2 on FreeBSD 8.3-RELEASE-p5 and am having things break
down when I try to run initdb. I got in contact with the pgsql-general
mailing list and we debugged the
6 matches
Mail list logo
