Re: [Chicken-users] process-fork weirdness

[Peter Busser]

Hi!

> If the client tries to connect and the server isn't listening, the
> connect -- and write -- will fail. Neither version is correct; the
> second one just happens to work. You need to send some sort of message
> -- a signal? -- from the server process to let the main program know
> that it may begin connecting. You should do this after TCP-LISTEN but
> before TCP-ACCEPT, which blocks.

A simpler solution is to open the server socket before the forking and to 
close it in the client process.

Groetjes,
Peter.