On Tue, Apr 21, 2015 at 12:26 AM, Martin Pitt wrote:
> So I see no use case for idle timer based cleanup. Can you please
> explain why they are better than on-demand cleanup?
We do it on Pantheon's infrastructure because many daemons have a
resource footprint that is more than just allocated memo
My two cents is feature can be implemented as long as we get support
from the application. For example sd-event has the builtin support to
quit when it is idle. Systemd can pass the exit-on-idle timeout to the
application via env variables so the event loop can configure itself
to quit.
I am not s
Hello Kyungmin,
Kyungmin Park [2015-04-21 9:21 +0900]:
> At mobile. some daemon is not doing exact daemon task. it acts like
> app. so it's kill-able based on priority. now it can't know it's idle
> or not. In the app-like daemon developer, they don't want to exit
> since performance reason. but
On Tue, 21.04.15 09:21, Kyungmin Park (kmp...@infradead.org) wrote:
> > Well, we should make sure to not encourage people to write
> > suboptimal. And such an external timer-based notification is
> > necessarily suboptimal code: a well-behaving daemon would set a timer
> > the moment it notices it
On Tue, Apr 21, 2015 at 8:37 AM, Lennart Poettering
wrote:
> On Tue, 21.04.15 07:56, Kyungmin Park (kmp...@infradead.org) wrote:
>
>> On Tue, Apr 21, 2015 at 12:10 AM, Lennart Poettering
>> wrote:
>> > On Mon, 20.04.15 23:56, WaLyong Cho (walyong@samsung.com) wrote:
>> >
>> >> If a service do
On Tue, 21.04.15 07:56, Kyungmin Park (kmp...@infradead.org) wrote:
> On Tue, Apr 21, 2015 at 12:10 AM, Lennart Poettering
> wrote:
> > On Mon, 20.04.15 23:56, WaLyong Cho (walyong@samsung.com) wrote:
> >
> >> If a service does not consume CPU during some time(can be configured
> >> by ExitOn
On Tue, Apr 21, 2015 at 12:10 AM, Lennart Poettering
wrote:
> On Mon, 20.04.15 23:56, WaLyong Cho (walyong@samsung.com) wrote:
>
>> If a service does not consume CPU during some time(can be configured
>> by ExitOnIdleSec=) and set to stopped on idle state(ExitOnIdle=), the
>> service will be s
On 04/21/2015 12:10 AM, Lennart Poettering wrote:
> On Mon, 20.04.15 23:56, WaLyong Cho (walyong@samsung.com) wrote:
>
>> If a service does not consume CPU during some time(can be configured
>> by ExitOnIdleSec=) and set to stopped on idle state(ExitOnIdle=), the
>> service will be stopped. Th
On Mon, 20.04.15 23:56, WaLyong Cho (walyong@samsung.com) wrote:
> If a service does not consume CPU during some time(can be configured
> by ExitOnIdleSec=) and set to stopped on idle state(ExitOnIdle=), the
> service will be stopped. This can be useful if the service provides
> some of activa
This will be nice to have.
On Mon, Apr 20, 2015 at 10:56 AM WaLyong Cho
wrote:
> If a service does not consume CPU during some time(can be configured
> by ExitOnIdleSec=) and set to stopped on idle state(ExitOnIdle=), the
> service will be stopped. This can be useful if the service provides
> som
If a service does not consume CPU during some time(can be configured
by ExitOnIdleSec=) and set to stopped on idle state(ExitOnIdle=), the
service will be stopped. This can be useful if the service provides
some of activation methods.
---
src/core/load-fragment-gperf.gperf.m4 | 2 +
src/core/serv
11 matches
Mail list logo