I noticed one of the developers at The Ft. Lauderdale Office of The Corporation using the time of day to seed a random number generator, which is borderline okay (depending on how the resulting random numbers will be used) there are better ways to generate a random seed, at least on a modern POSIX [1] system—read data from /dev/urandom.
My fellow cow-orker B, with whom I was having this discussion, mentioned this borderline paranoid approach [2] to reading /dev/urandom. But I think that if you have to call fstat() to make sure the file is actually /dev/urandom then you have more things to worry about (really—if a cracker can substitute /dev/urandom with known data, it's pretty much game over [3]—B agreed with that statement, by the way). Besides, the author wasn't paranoid enough! Who's to say there isn't some extra code in there (say, via $LD_PRELOAD [4] or ptrace() [5] or maybe even through some ELF magic on the executable [6]) that intercepts the read() [7] function to return “random data” when reading from /dev/urandom? Hmmmm? (about the only thing you can do to counter that is nuke the site from orbit [8]—it's the only way to be sure)
But in the mean time, just use /dev/urandom [9].
[1] http://pubs.opengroup.org/stage7tc1/
[2] http://insanecoding.blogspot.com/2014/05/a-good-idea-with-bad-usage-devurandom.html
[3] https://www.youtube.com/watch?v=dsx2vdn7gpY
[4] http://stackoverflow.com/questions/426230/what-is-the-ld-preload-trick
[5] http://en.wikipedia.org/wiki/Ptrace
[6] http://www.exploit-db.com/papers/14087/
[7] http://pubs.opengroup.org/onlinepubs/009695399/functions/read.html
[8] https://www.youtube.com/watch?v=aCbfMkh940Q