[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#645469: marked as done (bind() fails for AF_UNIX sockets with EINVAL)

Your message dated Sat, 29 Oct 2011 01:26:22 -0500
with message-id <20111029062622.GA10846@elie.hsd1.il.comcast.net>
and subject line Re: bind() fails for AF_UNIX sockets with EINVAL
has caused the Debian Bug report #645469,
regarding bind() fails for AF_UNIX sockets with EINVAL
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
645469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645469
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: kfreebsd-9
Version: 9.0~svn225873
Severity: important

Hi,

Typical kfreebsd-amd64 experimental system.  When I try to use "cupt
update" after booting with kfreebsd 9, it always fails:

	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

For reference, the installed libc0.1 is 2.13-21.  Anyway, thought you
might like to know.

Regards,
Jonathan

--- End Message ---
--- Begin Message --- 
Version: 9.0~svn226626-1

Jonathan Nieder wrote:

> Typical kfreebsd-amd64 experimental system.  When I try to use "cupt
> update" after booting with kfreebsd 9, it always fails:
>
> 	E: unable to bind server socket to file '/tmp/cuptyL8GPC': Invalid argument
> 	E: error performing command 'update'

Seems to be fixed, or at least sufficiently worked around. :)  Thanks
to everyone who worked on this.

--- End Message ---
Reply to: