On 2/9/15, Andy Bradford <amb-fos...@bradfords.org> wrote: > Thus said Richie Adler on Mon, 09 Feb 2015 17:03:13 -0300: > >> WARNING: Device "/dev/null" is not available for reading and writing. >> >> WARNING: Device "/dev/urandom" is not available for reading. This >> means that the pseudo-random number generator used by SQLite will be >> poorly seeded. > > Are you running Fossil in a chroot/jail which doesn't have those > devices? >
I added those warnings specifically for the case of running Fossil inside a chroot jail with the those character devices. The /dev/urandom device is used to seed the PRNG inside of SQLite. Probably SQLite will be fine without it, but it is still nice to have. The /dev/null device is opened for writing if Fossil finds that its file-descriptor 2 is not open when it is launched. (Stunnel4 sometimes does this.) This is dangerous to run with file-descriptor 2 not open since it might get opened on a data file and then if an assert() fire, it will write to file-descriptor 2 and overwrite data. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
