From: kosaki.motohiro@... Date: 2014-02-20T08:58:23+00:00 Subject: [ruby-core:60898] [ruby-trunk - Bug #9525] [Closed] Stuck with Socket.pack_sockaddr_in Issue #9525 has been updated by Motohiro KOSAKI. Status changed from Third Party's Issue to Closed Backport changed from 1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN to 1.9.3: REQUIRED, 2.0.0: REQUIRED, 2.1: REQUIRED ---------------------------------------- Bug #9525: Stuck with Socket.pack_sockaddr_in https://bugs.ruby-lang.org/issues/9525#change-45303 * Author: Naotoshi Seo * Status: Closed * Priority: Normal * Assignee: * Category: * Target version: * ruby -v: 1.9.3p194 * Backport: 1.9.3: REQUIRED, 2.0.0: REQUIRED, 2.1: REQUIRED ---------------------------------------- We met this trouble with Fluentd https://github.com/fluent/fluentd. Fluentd is sometimes stuck at `Socket.pack_sockaddr_in` line on shutdown. Here is the gist https://gist.github.com/sonots/9047653 to explain details. -- http://bugs.ruby-lang.org/