[#7978] Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...>

This patch adds support for getting the uid and gid of the peer

27 messages 2006/06/09
[#8004] Re: Patch for Unix socket peer credentials — Tanaka Akira <akr@...17n.org> 2006/06/16

In article <200606091528.30171.jfh@cise.ufl.edu>,

[#8005] Re: Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...> 2006/06/16

On Friday 16 June 2006 11:51, Tanaka Akira wrote:

[#8010] Re: Patch for Unix socket peer credentials — Tanaka Akira <akr@...17n.org> 2006/06/17

In article <200606161327.35948.jfh@cise.ufl.edu>,

[#8191] Re: Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...> 2006/07/10

On Saturday 17 June 2006 06:27, Tanaka Akira wrote:

[#8193] Re: Patch for Unix socket peer credentials — Tanaka Akira <akr@...> 2006/07/11

In article <200607101352.16804.jfh@cise.ufl.edu>,

[#8212] Re: Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...> 2006/07/13

On Tuesday 11 July 2006 00:10, Tanaka Akira wrote:

[#8217] Re: Patch for Unix socket peer credentials — nobu@... 2006/07/14

Hi,

[#8257] Re: Patch for Unix socket peer credentials — "James F. Hranicky" <jfh@...> 2006/07/18

On Thursday 13 July 2006 22:48, nobu@ruby-lang.org wrote:

[#8258] Re: Patch for Unix socket peer credentials — Eric Hodel <drbrain@...7.net> 2006/07/18

On Jul 18, 2006, at 12:27 PM, James F. Hranicky wrote:

[#8073] 1.8.5p1 build failure on Solaris 10 — "Daniel Berger" <Daniel.Berger@...>

Solaris 10

23 messages 2006/06/27
[#8074] Re: 1.8.5p1 build failure on Solaris 10 — Yukihiro Matsumoto <matz@...> 2006/06/28

Hi,

[#8078] Re: 1.8.5p1 build failure on Solaris 10 — "Daniel Berger" <Daniel.Berger@...> 2006/06/28

Yukihiro Matsumoto wrote:

[#8079] Re: 1.8.5p1 build failure on Solaris 10 — ts <decoux@...> 2006/06/28

>>>>> "D" == Daniel Berger <Daniel.Berger@qwest.com> writes:

[#8096] Re: 1.8.5p1 build failure on Solaris 10 — ville.mattila@... 2006/06/29

ts <decoux@moulon.inra.fr> wrote on 28.06.2006 17:37:00:

Re: Windows XP SP2 socket issues

From: "Dan Hatfield" <dan.hatfield@...>
Date: 2006-06-07 01:13:34 UTC
List: ruby-core #7966
|Can you explain it more?
|Do you mean that there are some bugs?

Sorry, I didn't mean to apply there were bugs with the patch. I think the
patch is fine - it works great in 1.9...I assume it is something about the
way I applied the patch and compiled the binaries on my machine.

|Ruby 1.8 is compiled with winsock1, not winsock2.
|To maintain the binary compatibility, I didn't scheduled to
|backport the patch (which need to use winsock2).

|However, in answer to your request, I decide to prepare a
|little mechanism in 1.8.
|In using a new configure option, users come to be able to
|select whether to use winsock2.

|I'll commit it later into 1.8, with ifs sockets patch.

That would be great! Very much appreciated!!!



On 6/6/06, U.Nakamura <usa@garbagecollect.jp> wrote:
>
> Hello,
>
> In message "Windows XP SP2 socket issues"
>     on Jun.06,2006 00:32:48, <dan.hatfield@gmail.com> wrote:
> | That's a bit naive I know. :) Interestingly, it generally appears to
> work
> | but I appear to be blowing up when it tries to close the socket now.
>
> Can you explain it more?
> Do you mean that there are some bugs?
>
>
> | My questions are:
> |
> | 1) Is there any effort to get this ifs sockets patch into 1.8 currently?
> | With 1.9 being an experimental branch and Ruby 2.0 not coming anytime
> soon,
> | I'm thinking this problem will be growing an importance as more people
> end
> | up on XP SP2.
> |
> | 2) Or should I just continue down the path of recompiling my own
> binaries?
> | And if so, is there anyone out there that knows enough about these ifs
> | sockets to help me debug my patch?
> |
> | 3) Or am I better off trying to get rails to run under 1.9 (that may not
> be
> | a question for this list, I can post in on rails devel)?
> |
> | 4) Or should I just punt and go for a dual boot with FreeBSD or
> something?
> | :)
>
> Ruby 1.8 is compiled with winsock1, not winsock2.
> To maintain the binary compatibility, I didn't scheduled to
> backport the patch (which need to use winsock2).
>
> However, in answer to your request, I decide to prepare a
> little mechanism in 1.8.
> In using a new configure option, users come to be able to
> select whether to use winsock2.
>
> I'll commit it later into 1.8, with ifs sockets patch.
>
>
> Regards,
> --
> U.Nakamura <usa@garbagecollect.jp>
>
>
>
>

In This Thread

Prev Next