Can anyone do me a favor and let me know whether this short guide, along
with the correction described in the comments, is correct?
https://trac.torproject.org/projects/tor/ticket/13702
Hmm, have you been keeping an eye on your logs? I eventually got a
warning telling me that Tor had to stop opening connections because it
couldn't open any more files. Regardless, Tor frequently opens thousands
of files, while the default hard limit for OpenBSD users is 512-1024
files. My Linux nod
M, li...@ggp2.com wrote:
> On Fri, Nov 21, 2014 at 12:30:57PM -0500, Libertas wrote:
>> Hmm, have you been keeping an eye on your logs? I eventually got a
>> warning telling me that Tor had to stop opening connections because it
>> couldn't open any more files. Regard
21, 2014 at 12:30:57PM -0500, Libertas wrote:
>> Hmm, have you been keeping an eye on your logs? I eventually got a
>> warning telling me that Tor had to stop opening connections because it
>> couldn't open any more files. Regardless, Tor frequently opens thousands
>>
On 11/27/2014 07:38 AM, Raimo Niskanen wrote:
> I have also learned to use the -C flag to patch...
Have we ever considered changing the suggested shell commands in the
patches to ensure that the patch will apply cleanly before trying? We
could wrap the actual patch command an if-block with a 'patc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/02/2014 08:49 PM, Einfach Jemand wrote:
> Hmm, I checked on one of my boxen and there /etc/passwd has
>
> _squid ^! Note the underline.
>
> as account for this package, so you probably want
>
> _squid:\
I'm pretty sure it's supp
Some of the people at tor-...@lists.nycbug.org and I are trying to
figure out why Tor relays under-perform when running on OpenBSD. Many
such relays aren't even close to being network-bound,
file-descriptor-bound, memory-bound, or CPU-bound, but relay at least
33-50% less traffic than would be expe
I also completely forgot to mention the below warning, which Tor
0.2.5.10 (the current release) gives when run on OpenBSD 5.6-stable amd64:
> We were built to run on a 64-bit CPU, with OpenSSL 1.0.1 or later,
> but with a version of OpenSSL that apparently lacks accelerated
> support for the NIST
to system call statistics and other ways
to find the problem here. I'm very new to this, so suggestions on tools
and techniques are appreciated.
On 12/31/2014 06:47 PM, Carlin Bingham wrote:
> On Thu, 1 Jan 2015, at 11:49 AM, Libertas wrote:
>> I also completely forgot to mention the
I've tuned PF parameters in the past, but it doesn't seem to be the
issue. My current pfctl and netstat -m outputs suggest that there are
more than enough available resources and no reported failures.
I remember someone on tor-...@list.nycbug.org suggesting that it could
be at least partially due
I'm relatively new to OpenBSD, so please correct any mistakes below.
As you may know, resolv.conf.tail is appended to resolv.conf. This is
convenient because the last 'search' and 'domain' keywords listed are used.
However, nameservers are queried in the order they are listed. This
means (if I un
uld like to run OpenBSD with them.
Personally, I got $100 of credit from the Github Student Developer Pack
(and you can too, if you're a college student:
https://education.github.com/), and I'd rather be running OpenBSD on it
than Debian or FreeBSD.
Libertas
On 01/26/2015 05:05 AM, John Long wrote:
> Is anybody using a regular USB stick as a primary disk drive for OpenBSD and
> if so how well do they work and how long do they last? Is this a reasonable
> solution for an appliance or dev box and are there better alternatives that
> will work over USB or
13 matches
Mail list logo
