| Age | Commit message (Collapse) | Author |
|---|
|
* user is different
* user must not be managed
* make access more safe, it doesn't make sense that the user running
the daemon owns the config, nor the config directory.
|
|
tor_connections started blocking and I wasn't able to find the root
cause for it nor an updated version of the plugin.
This also blocked munin itself, which had the issue that the node
disappeared within munin.
Based on https://lists.torproject.org/pipermail/tor-talk/2006-June/010486.html
it seems to more or less match the open filedescriptors and hence
we monitor rather this than rely on a unmanageable plugin.
The only drawback is that this must run as root, as non-root users
can't read the filedescriptors from proc.
|
|
|
|
|
|
By extracting the resources to their own class we can avoid a bug
in puppet that makes it hard to deal with inherited parametrized
classes.
|
|
|
|
Puppet style guide "9.6. File Modes" reads:
In addition, file modes should be specified as single-quoted strings instead
of bare word numbers.
|
|
Puppet style guide "9.2. Arrow Alignment" reads: "All of the fat comma arrows
(=>) in a resource’s attribute/value list should be aligned. The arrows should
be placed one space ahead of the longest attribute name."
|
|
Puppet style guide, section "8. Quoting", reads: "All strings that do not
contain variables should be enclosed in single quotes."
|
|
/usr/share/tor/tor-service-defaults-torrc exists and contains:
CookieAuthentication 1
CookieAuthFileGroupReadable 1
CookieAuthFile /var/run/tor/control.authcookie
|
|
|
|
|
