Re: [fossil-users] getting rid of warning can't open /dev/null...
On 5/26/2015 3:02 PM, Richard Hipp wrote: On 5/26/15, Will Parsons varro@nodomain.invalid wrote: On Tuesday, 26 May 2015 3:20 PM -0400, Richard Hipp wrote: 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 While you're at it, you may optionally do: mkdir /jail/etc cp /etc/localtime /jail/etc so your timeline isn't locked to UTC. You will also need to use the web administration interface to configure the timeline to show in local time. This should be documented on the Fossil website someplace Yes, please. -- Andy Goth | andrew.m.goth/at/gmail/dot/com signature.asc Description: OpenPGP digital signature ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] getting rid of warning can't open /dev/null...
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
[fossil-users] getting rid of warning can't open /dev/null...
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? -- Will ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] getting rid of warning can't open /dev/null...
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.) There is no setting to run that warning off. But you can comment-out the code. https://www.fossil-scm.org/fossil/info/97d246c3?ln=80-90 -- 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
Re: [fossil-users] getting rid of warning can't open /dev/null...
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. There is no setting to run that warning off. But you can comment-out the code. https://www.fossil-scm.org/fossil/info/97d246c3?ln=80-90 OK - I'll have to consider if the annoyance of the warnings is enough for me to want to maintain a patched version of Fossil. Thanks for the info. -- Will ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
