> Hm, if the Chromium kernel/LSM forbids this, I don't see how this can be
> fixed in systemd? Do you?
Obviously the answer is no... i reported here since the commands in
the service file were working fine when executed by hand, so i thought
it couldn't be a kernel issue, but how systemd handled t
Am 22.07.2015 um 17:42 schrieb nfb:
>> Are you suspecting the arm architecture or the custom kernel to be the
>> culprit? Can you test the stock Debian kernel on arm?
>> Your custom kernel, does it have every option enabled as specified in
>> /usr/share/doc/systemd/README.gz
>
> Yes i suspect abou
> Are you suspecting the arm architecture or the custom kernel to be the
> culprit? Can you test the stock Debian kernel on arm?
> Your custom kernel, does it have every option enabled as specified in
> /usr/share/doc/systemd/README.gz
Yes i suspect about the kernel, also because among the error l
Hi
Am 22.07.2015 um 15:58 schrieb nfb:
> As i suspected there is no such issue on my main x86 laptop running
> the same distro and updated software. The only difference is the arm
> architecture and the custom kernel, as i noticed before.
Are you suspecting the arm architecture or the custom kern
As i suspected there is no such issue on my main x86 laptop running
the same distro and updated software. The only difference is the arm
architecture and the custom kernel, as i noticed before.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe".
Control: forwarded -1 https://github.com/systemd/systemd/issues/567
Am 13.07.2015 um 01:04 schrieb nfb:
>> Once you file the bug upstream, reply to *this* bug report with the
>> upstream bug report number.
>> This way I can link the two bug reports and we can track the upstream
>> process automati
> Once you file the bug upstream, reply to *this* bug report with the
> upstream bug report number.
> This way I can link the two bug reports and we can track the upstream
> process automatically.
here it is:
https://github.com/systemd/systemd/issues/567
@Intrigeri
So you cannot confirm... mayb
Hi,
Am 12.07.2015 um 23:41 schrieb nfb:
>> That said, this sounds like an upstream issue, so please report that at
>>
>> https://github.com/systemd/systemd/issues/
>>
>> and report bug with the bug number.
>
> Sorry, do i have to file an upstream bug referring to this bug number in its
> body, or
nfb wrote (12 Jul 2015 21:41:39 GMT) :
> Oh yes i didn't specify i installed the tor package in the debian testing
> repos, so the unit file is the one included in the package:
FWIW, I'm using the same unit file (from sid) and it has been working
flawlessly here since it was introduced in the tor
> Including the complete .service file would be helpful.
Oh yes i didn't specify i installed the tor package in the debian testing
repos, so the unit file is the one included in the package:
---
[Unit]
Description=Anonymizing overlay network for TCP
After=network.target nss-lookup.target
[Servi
Control: tags -1 + upstream
Am 12.07.2015 um 15:30 schrieb nfb:
> After a quick jump on the #tor IRC channel we concluded that this may
> be an issue on the systemd side, and after reading something around
> the web we tried to tweak the Hardening section of the unit file. And
> indeed we found tha
Package: systemd
Version: 221-1
Severity: normal
Dear Maintainer,
I installed tor (The onion router) the other day and when i started it
(either via /usr/sbin/service or systemctl) i went through this:
$ sudo systemctl start tor.service
Job for tor.service failed because the control process exi
12 matches
Mail list logo
