On Feb 27, 2007, at 8:40 AM, Perrin Harkins wrote:
That seems very unlikely to me, unless you are using it in a way that
doesn't cause it to connect before forking. You can't open sockets,
fork and then use the same socket in both processes.
Right now I connect pre-fork in the parent -- it works fine.
I suggest loading the module in the parent but not opening any
connections until after the fork.
Maybe its closing the socket and opening it again? I don't know.
Maybe its doing all of the connection through the global namespace ?
In my setup, its definitely connecting pre-fork and working in
multiple children.
// Jonathan Vanasco
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| SyndiClick.com
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| FindMeOn.com - The cure for Multiple Web Personality Disorder
| Web Identity Management and 3D Social Networking
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
| RoadSound.com - Tools For Bands, Stuff For Fans
| Collaborative Online Management And Syndication Tools
| - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - - - - - - - - - - - - - - - -
