Comments on: The hidden corners of Passenger http://izumi.plan99.net/blog/index.php/2008/04/26/the-hidden-corners-of-passenger/ Ecchi nanowa ikenai to omoimasu Fri, 09 Apr 2010 11:42:43 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: macournoyer http://izumi.plan99.net/blog/index.php/2008/04/26/the-hidden-corners-of-passenger/comment-page-1/#comment-8819 macournoyer Sun, 27 Apr 2008 14:42:04 +0000 http://izumi.plan99.net/blog/index.php/2008/04/26/the-hidden-corners-of-passenger/#comment-8819 Indead, I was wrong. I was under that impression because EventMachine deletes the file before binding to it. My point is that those 2 problems have been solved already. Although your solutions are more elegant. Indead, I was wrong. I was under that impression because EventMachine deletes the file before binding to it. My point is that those 2 problems have been solved already. Although your solutions are more elegant.

]]> By: Hongli http://izumi.plan99.net/blog/index.php/2008/04/26/the-hidden-corners-of-passenger/comment-page-1/#comment-8818 Hongli Sun, 27 Apr 2008 11:38:33 +0000 http://izumi.plan99.net/blog/index.php/2008/04/26/the-hidden-corners-of-passenger/#comment-8818 <blockquote>While I agree it’s better to remove the unix socket file, multiple socket can listen on the same file, so if the file already exist no error will happen. That means, it’s not required to remove the file if the process crashed.</blockquote> Is that really so? <pre>[hongli@hoshino ~]$ irb >> require 'socket' => true >> s1 = UNIXServer.new('foo.sock') => #<UNIXServer:foo.sock> >> s1.close => nil >> s2 = UNIXServer.new('foo.sock') Errno::EADDRINUSE: Address already in use - foo.sock from (irb):4:in `initialize' from (irb):4:in `new' from (irb):4 from :0 >> </pre>

While I agree it’s better to remove the unix socket file, multiple socket can listen on the same file, so if the file already exist no error will happen. That means, it’s not required to remove the file if the process crashed.

Is that really so?

[hongli@hoshino ~]$ irb
>> require 'socket'
=> true
>> s1 = UNIXServer.new('foo.sock')
=> #<UNIXServer:foo.sock>
>> s1.close
=> nil
>> s2 = UNIXServer.new('foo.sock')
Errno::EADDRINUSE: Address already in use - foo.sock
        from (irb):4:in `initialize'
        from (irb):4:in `new'
        from (irb):4
        from :0
>>
]]> By: macournoyer http://izumi.plan99.net/blog/index.php/2008/04/26/the-hidden-corners-of-passenger/comment-page-1/#comment-8817 macournoyer Sun, 27 Apr 2008 02:00:47 +0000 http://izumi.plan99.net/blog/index.php/2008/04/26/the-hidden-corners-of-passenger/#comment-8817 While I agree it's better to remove the unix socket file, multiple socket can listen on the same file, so if the file already exist no error will happen. That means, it's not required to remove the file if the process crashed. Also Thin and Mongrel do remove stale pid files on start. While I agree it’s better to remove the unix socket file, multiple socket can listen on the same file, so if the file already exist no error will happen. That means, it’s not required to remove the file if the process crashed.

Also Thin and Mongrel do remove stale pid files on start.

]]>