On Sun, 2 Apr 2006, Kris Kennaway wrote:
Right, but why are they doing it *consistently* in FreeBSD 6.x, when they
never did it in FreeBSD 4.x? I have postmaster processes running on the
FreeBSD box as far back as November 27th, 2005 ... and have *never*
experienced this problem ... so it isn't PostgreSQL that has changed,
something in FreeBSD has changed :(
You'll need to do some debugging to find out which of the two causes
of EINVAL are true here (or some undocumented cause).
'k, right now, the checks in PostgreSQL are just seeing if the result of
semctl < 0 ... i see from the man page what 'two values' of EINVAL you are
referring to ... but, if they both return the same ERRNO, how do I
determine which of the two is the cause of the problem? :(
----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email: [EMAIL PROTECTED] Yahoo!: yscrappy ICQ: 7615664
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
