On 5/26/15, Will Parsons <varro@nodomain.invalid> wrote: > On Tuesday, 26 May 2015 3:20 PM -0400, Richard Hipp wrote: >> On 5/26/15, Will Parsons <varro@nodomain.invalid> wrote: >>> Apparently a change was made to Fossil in February to issue warnings >>> about not being able to open /dev/null and /dev/urandom. I'm running >>> a Fossil server from inetd under FreeBSD, and am getting these >>> messages when I go into Administration. Since I can't do anything >>> about the underlying reason (at least, I don't think I can), can I do >>> anything to suppress the messages? >>> >> >> I think the best solution is to actually create a /dev/null and >> /dev/urandom inside of your chroot jail. (That's what the >> www.fossil-scm.org website does.) > > Unfortunately, I have no idea how to that.
mkdir /jail/dev mknod /jail/dev/null c 1 3 mknod /jail/dev/urandom c 1 9 The above works for Linux. Something similar will probably work on NetBSD - I dunno. The magic constants might change, though. Find the correct values by using "ls -l /dev/null" and "ls -l /dev/urandom". Adjust the "/jail" path appropriately. You'll need to be root to do this. This should be documented on the Fossil website someplace.... -- 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
