From: Olaf Lenz <olenz@Physik.Uni-Bielefeld.DE>
To: GSL Discussion List <gsl-discuss@sources.redhat.com>
Subject: Re: Random Number Seed
Date: Tue, 22 Feb 2005 08:19:00 -0000 [thread overview]
Message-ID: <421AEAF8.4090204@physik.uni-bielefeld.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0502210726120.7876@lilith.rgb.private.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello!
Robert G. Brown wrote:
|> My bad, sorry. I was assuming that the system itself wasn't broken
|> here, so that /dev/random might be absent but wouldn't be broken.
[clip]
I do not blame you for the code! I would have probably written the same
code myself.
I was thinking along the same lines as you - that our system is broken.
It turned out that the problem is the queuing system "condor" that we
use. Condor wraps the system calls of the executable with its own
versions, and these lead to the strange behaviour described: the fopen()
call succeeds, the fread() returns 0 and does not set the seed, and
feof() is set.
Olaf
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCGur4tQ3riQ3oo/oRAmJSAJwNt2sWgY8YpQIZS+pICMpTWeqaGgCgoTCR
sNVXLTsHH88RCWoRbY3Q1Gc=
=Hweq
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-02-22 8:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 16:03 Przemyslaw Sliwa
2004-03-01 16:53 ` Frederick Joseph Ross
2004-03-01 17:55 ` Robert G. Brown
2004-03-01 20:06 ` Daniel T Konkle
2005-02-21 11:55 ` Olaf Lenz
2005-02-21 12:03 ` Jerome BENOIT
2005-02-21 12:47 ` Robert G. Brown
2005-02-22 8:19 ` Olaf Lenz [this message]
2004-03-04 17:42 ` Brian Gough
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=421AEAF8.4090204@physik.uni-bielefeld.de \
--to=olenz@physik.uni-bielefeld.de \
--cc=gsl-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).