Am 15.02.2020 um 08:31 schrieb Petr Štetiar:
> e9hack [2020-02-15 08:24:23]:
>
>> Feb 15 08:17:20.000 [warn] Unable to open "/var/run/tor.pid" for writing:
>> Permission denied
>> Feb 15 08:17:20.000 [err] Unable to write PIDFile "/var/run/tor.pid"
>
> This is probably needed in the init script
e9hack [2020-02-15 08:24:23]:
> Feb 15 08:17:20.000 [warn] Unable to open "/var/run/tor.pid" for writing:
> Permission denied
> Feb 15 08:17:20.000 [err] Unable to write PIDFile "/var/run/tor.pid"
This is probably needed in the init script:
procd_set_param user tor
-- ynezz
Hi,
tor doesn't start since commit ca6528f002d74445e3d0a336aeb9074fc337307a:
tor: update init script
Changes:
-add uci config
-create pid file by procd
-add reload function
Feb 15 08:17:20.000 [warn] Unable to open "/var/run/tor.pid" for writing:
Permission denied
Feb 15 08:17:20.000 [err] Una
* send: cleanup skb padding calculation
* socket: remove useless synchronize_net
Sorry for the back-to-back releases. This fixes a regression spotted by Eric
Dumazet.
Signed-off-by: Jason A. Donenfeld
---
package/network/services/wireguard/Makefile | 4 ++--
1 file changed, 2 insertions(+), 2 d
This adds support for the various clones of the TL-WA830RE recently
supported in fb99ac6807f2 ("ath79: add support for TP-Link TL-WA830RE v1"):
- tplink,tl-wa701nd-v1
- tplink,tl-wa730re-v1
- tplink,tl-wa801nd-v1
- tplink,tl-wa830re-v1 (already supported)
- tplink,tl-wa901nd-v1
Since these device
Update linux-firmware to 20200122
git log --pretty=oneline --abbrev-commit 20191215..20200122
1eb2408 linux-firmware: Update firmware file for Intel Bluetooth AX200
0dc1611 linux-firmware: Update firmware file for Intel Bluetooth AX201
d03f79c linux-firmware: Update firmware file for Intel Blueto
* chacha20poly1305: defensively protect against large inputs
Defense-in-depth sort of check.
* netns: ensure that icmp src address is correct with nat
We finally upstreamed the last remaining compat.h hack in this patch series:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net.git/commi
Hi,
since 19.07 release we have changed device/image names in several targets to
make naming schemes in OpenWrt more systematic and harmonize them between
targets.
Today, I have also renamed most of the brcm target for a similar reason.
To aid downstream and other developers to keep overview
Hi everyone,
I am sorry for my late reply to this thread. My email provider flagged
it as spam, so I only saw the conversation now. It seems that you have
reached a conclusion on how to proceed, but I thought I should anyway
share my notes/observations on this issue (in case they can be
useful).
