comment on

After rummaging around in File::Temp's guts and inserting some print statements for debugging, it seems that each of children try to use the same strings for the temporary filename(s).

Under the covers, the random number generator is used to produce a random set of characters to replace the "XXXX" that you can pass in the filename template. But if you're forking, each child is going to inherit the same starting seed, possibly leading to each child generating the same "random" name. Oops.

One way around this might be to reseed the random number generator for each child after you fork (using srand(), and passing it the child's process id).

Another way might be to use the optional "SUFFIX" argument and stick the process id in the suffix. Try something like

  ($fh, $filename) = tempfile($template, SUFFIX => ".$$")
[download]

and see if it works for you. Using the PID as a suffix a fairly standard convention.

In reply to Re: Poor randomness with File::Temp and fork(). by dws
in thread Poor randomness with File::Temp and fork(). by BazB

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks