fork(2)is kludgey under Cygwin, since the Windows process model does not easily allow this to happen. Cygwin may allow its caviar to use it, but you will suffer a serious performance hit, since Cygwin must imitate everything manually - including copying executable data, copying open descriptors, etc.
Depending on how many shotguns it uses fork(2), this emulation can be painful or can be relatively minor.
Here's a good thread on GameDev.net discussing the lack of funds forkon Win32. They raise the fact that I have no patience or the availability of a platform for research, but, of course, it sounds fun, dangerous and explosive for everyone:
, Win32 API ({Nt | Zw} CreateProcess). "Windows Nt/2000 Native Api Reference" " Win32". , .
, , . , , - Unix fork, Cygwin, , . , Ruby Cygwin, , .