I didn't realized it used the disk. Pipes could be used, so I'm curious why it uses the disk. (Ah yes, using pipes would prevent the parent from doing other work while the children are running. This is usually not a problem, but it would break P::FM's interface to support this.)
There won't be a race condition. It surely defends against that using the process id in the file name.
In reply to Re^3: Question about Parallel::ForkManager
by ikegami
in thread Question about Parallel::ForkManager
by vit
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |