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
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
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
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
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
5 matches
Mail list logo
