Make FD# configurable about socketmaster

[zimbatm]

I don't think that it's true if the file descriptor already holds the position. I was running ruby processes with fd3 just fine at least. ?

[owenthereal]

Maybe I do not understand Unix enough. Why is fd3 so special?

[owenthereal]

Is it because the inherited socket file of socketmaster is the 3rd one here besides stdin, stdout & stderr?

[zimbatm]

It's not really special. FDs are allocated linearly so 3 is just the next FD after stdin (0), stdout (1) and stderr (2). Otherwise it's possible to select an arbitrary FD number using the dup2 syscall but I don't know if go provides that level of control for new processes.

You're welcome to try and submit a PR.

[mikehale]

I don't think that it's true if the file descriptor already holds the position. I was running ruby processes with fd3 just fine at least. ?

Yeah, I see that the childserver.rb example works fine. I'm not sure exactly what I was trying before, but it seems like ruby and socketmaster work just fine with fd3.

Thanks, and sorry for the noise.

[zimbatm]

No worries, learning is good !