X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Thu, 7 Mar 2013 10:40:54 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Socket bug in 20130301 snapshot Message-ID: <20130307094054.GA30272@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Mar 6 17:45, Yaakov (Cygwin/X) wrote: > The recent changes to fhandler_socket::bind in the 20130301 32bit > snapshot have broken D-Bus. Attempting to start the messagebus > service fails with the following log message: > > Failed to start message bus: Failed to bind socket > "/var/run/dbus/system_bus_socket": File name too long Does D-Bus create 108 byte long AF_LOCAL socket names? Or, in other words, does D-BUS expect to be able using every single byte available in the sockaddr_un structure? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple