When you look at the user graphs, many of them show a weekly cycle.
What's our explanation for why this occurs?
I notice it strongly when I look at the graphs for the meek pluggable
transport, where usage is high on weekdays and lower on weekends. The
same thing happens in some per-country graphs.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
>> I'll prepare a unit file for this and add it to the trac entry.
a first version is there
https://bugs.torproject.org/14995
>> Weasel wrote:
>>> Tor trac is not the place to discuss Debian packaging
>>> enhancements
>
> Right. In the specific c
Thanks everyone for voting, based on your vote I am picking the
following date and time for our meeting:
*Thursday March 19th, 13:30UTC at #tor-dev*
We created a spreadsheet with all the tickets we need to triage:
https://docs.google.com/spreadsheets/d/1H_kAcQQ-NpGpKWG9RlF3w-NhruKKE9EZJcRaXBQGVy
(Trying to get these back onto a regular schedule now that dev-meeting
madness is over.)
Just wanted to remind you that the regular biweekly pluggable transports
meeting is going to occur tomorrow at 16:00 UTC. Place is the #tor-dev
IRC channel in the OFTC network.
https://trac.torproject.org/pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Zack Weinberg:
> On Tue, Mar 17, 2015 at 12:55 PM, Nusenu
> wrote:
>> I had:
Log debug file /var/log/tor/log
>> but it is not being written to.
>
> This is *probably* because one of the missing privileges is the
> ability to write to files in
On Tue, Mar 17, 2015 at 12:55 PM, Nusenu wrote:
> I had:
>>> Log debug file /var/log/tor/log
> but it is not being written to.
This is *probably* because one of the missing privileges is the
ability to write to files in /var/log/tor. Try `Log debug stderr`
instead -- you'll have to fish the logs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello Zack,
thanks for your answer.
Zack Weinberg:
> Could you please put
>
> Log debug /tmp/tor-startup.log
I had:
>> Log debug file /var/log/tor/log
but it is not being written to.
(I disabled ExecStartPre for now).
> in your torrc, try to st
Could you please put
Log debug /tmp/tor-startup.log
in your torrc, try to start the daemon with NoNewPrivileges=yes, and
then post the contents of /tmp/tor-startup.log ? We need to know
exactly how it's failing. (We might actually need you to run it under
`strace`, even.)
zw
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I'm currently preparing/testing a systemd unit file (#14995) for
debian (wheezy-backports/systemd 204) based on the one shipped by tor [1].
It does not work yet, and although the 'fix' would be easy - simply
remove:
NoNewPrivileges = yes
I'd li
Nusenu wrote (17 Mar 2015 12:15:22 GMT) :
> intrigeri:
>> Just for the record, we've discussed this a few months ago with
> Is there a trac entry?
I don't think so.
> I'll prepare a unit file for this and add it to the trac entry.
\o/
> Weasel wrote:
>> Tor trac is not the place to discuss Debi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
intrigeri:
> Nusenu wrote (16 Mar 2015 14:09:13 GMT) :
>> many relay operators run multiple tor instances to overcome
>> certain limitations. Currently the official deb packages do not
>> come with an easy configurable way to run multiple tor
>> inst
Hi,
Nusenu wrote (16 Mar 2015 14:09:13 GMT) :
> many relay operators run multiple tor instances to overcome certain
> limitations. Currently the official deb packages do not come with an
> easy configurable way to run multiple tor instances.
Just for the record, we've discussed this a few months
12 matches
Mail list logo
