gen_tcp:controlling_process

Jay Nelson <>
Thu Feb 27 08:33:01 CET 2003


When is gen_tcp:controlling_process necessary?

I have a function that is blocking on an accept call
waiting for a Socket connection.  When it gets one,
it spawns a new process, passes the Socket, and
then starts accept again.  The new process is able
to read the Socket without having been given access
by gen_tcp:controlling_process.  Is that normal?

I am running on RedHat 7.3 x86 architecture.

jay



More information about the erlang-questions mailing list