2011/10/16 Jonathan Nieder <jrnie...@gmail.com>:
>        E: unable to bind server socket to file '/tmp/cuptyL8GPC': Invalid 
> argument
>        E: error performing command 'update'
>
> By contrast, kfreebsd-image-8.2-1-amd64 8.2-8+gcc45 works fine.
>
> Trying to track this down, I tried the example from the bind(2)
> manpage (from manpages-dev 3.32-0.2), with MY_SOCK_PATH set to
> "/tmp/somepath" so it wouldn't require root permissions.  Same story
> there --- the 8.2 kernel works fine, while kfreebsd 9 gives me
>
>        bind: Invalid argument

Upstream just added an EINVAL condition in bind(2) to fix #645377 (see
http://security.freebsd.org/patches/SA-11:05/unix.patch).  Maybe this
is a collateral effect?

Could you check with 9.0~svn225586-1 [1] (which unlike 9.0~svn225873
doesn't have the security fix), or with 8.2-9 [2] (which unlike 8.2-8
*does* have it)?

Btw 8.2-9 is urgency=high, if it's affected by #645469 please let us
know ASAP so we can put its migration on hold.

[1] http://snapshot.debian.org/package/kfreebsd-9/9.0~svn225586-1/
[2] currently preparing an upload, will be in incoming in an hour or so

-- 
Robert Millan



--
To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAOfDtXN=Y8rATF_YpG5fxeO-MorJ4VcOaVi=orh_4mumfyp...@mail.gmail.com

Reply via email to