how can i share socket fd?

Anon

i used function pcntl_fork().
so i made some child process.
parent process accepted socket fd.
then now. how can child process share parent's socket fd?
is this possible?

majik-sheff

What?

van__

What?!?!?

He spawned a child process with pcntl_fork and the child is sharing the same socket with the parent. The problem is, how does he make the parent talk to the child and vice-versa.

I have this same issue with my daemon process server, but I only had a couple hours to play with it since I'm busy on my client load right now. (ALMOST DONE WOOOOOOHOOOOOO!!!)

But, my thinking on this was that I'd give the child it's own socket on a succesful fork and then connect back to the parent socket to create two way communication between the two.

Of course, that would take a new connection by the client if they were to be connected to the childs socket.

So that leads to my own question:
Is there anyone besides Majik Scheff that isn't making a forked process server with PHP these days?

majik-sheff

Forgive me, oh fork-meister. I suppose you use Linux, too? Get a real OS: www.freebsd.com

:^P

Anon

i am sorry.
my question was wrong. forgive me plz.
how can (child process'socket fd) communicate with (each other's child process's socket fd)?

first child process socket fd <-------communicate--------> second child process socket fd

is this possible?

majik-sheff

I don't know what Van has to say on the subject, but I believe you would need to have the parent pass messages between children (unless you set up some sort of shared memory).

van__

Yes, reread my first message.

When you spawn a child, give that child it's own socket and list of all open sockets for it's siblings.
Then, have the child make connections to the desired siblings socket and pass data to it.

What's happening here is that when you spawn a process, that process detaches from the parent and becomes it's own file (the .pid) even though you are still connected to the child via the parents port, your client maintians it's connection to the new child and not the parent. The child can talk to the parent, but can't recieve from it (or so I've seen... I'm still kind of new to this area as well) As far as I know, you can't just pass data from process to process without a socket connection since each process would be a user in it's own shell.

So as I said before, set up a new socket for each child and have them connect to each other to pass data back and forth.

For user one:
client -> parent.server on port 10000 -> forks child which opens port 12000

Client reconnects to port 12000 to control child process.

for user two:
another_client -> parent.server on port 10000 -> forks child which opens port 12001
Client reconnects to port 12001 to control child process.

for multiuser:

a two-way socket connection is established that is read/writable by both users for the duration of their connection.