Am 28.01.2017 um 00:02 schrieb Michael Biebl:
>
>
> Am 27. Januar 2017 21:16:52 MEZ schrieb Michael Gebetsroither
> :
>> On 2017-01-27 20:50, Michael Biebl wrote:
>>
The error sent from systemd back to systemd-run seems to be:
"Unit run-24908.scope already exists."
Am 27. Januar 2017 21:16:52 MEZ schrieb Michael Gebetsroither
:
>On 2017-01-27 20:50, Michael Biebl wrote:
>
>>> The error sent from systemd back to systemd-run seems to be:
>>> "Unit run-24908.scope already exists."
>>
>>
>> Could you check if you have many scope units in
On 2017-01-27 20:50, Michael Biebl wrote:
>> The error sent from systemd back to systemd-run seems to be:
>> "Unit run-24908.scope already exists."
>
>
> Could you check if you have many scope units in /run which could slow down
> systemd
# find /run/systemd/system/ -type f -iname '*.scope'
Am 27. Januar 2017 18:56:31 MEZ schrieb Michael Gebetsroither
:
>On 2017-01-24 20:20, Michael Biebl wrote:
>Hi Michael,
>
>>> The creation of scopes with systemd-run --scope is unreliable.
>>> It seems to depend on system "load" or some other factors affected
>>> by system
On 2017-01-24 20:20, Michael Biebl wrote:
Hi Michael,
>> The creation of scopes with systemd-run --scope is unreliable.
>> It seems to depend on system "load" or some other factors affected
>> by system "load".
>> On production systems we've seen an error rate of up to 20%.
>
>> % for i in `seq
Am 24.01.2017 um 16:13 schrieb Michael Gebetsroither:
> Source: systemd
> Version: 215-17+deb8u5
> Severity: normal
>
> Dear Maintainer,
>
> The creation of scopes with systemd-run --scope is unreliable.
> It seems to depend on system "load" or some other factors affected
> by system "load".
>
Source: systemd
Version: 215-17+deb8u5
Severity: normal
Dear Maintainer,
The creation of scopes with systemd-run --scope is unreliable.
It seems to depend on system "load" or some other factors affected
by system "load".
On production systems we've seen an error rate of up to 20%.
It feels the