From: Alessandro Di Marco <dmr@gmx.it>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: [ANNOUNCE] System Inactivity Monitor v1.0
Date: Tue, 23 Jan 2007 18:11:38 +0100 [thread overview]
Message-ID: <87lkjthdmd.fsf@gmx.it> (raw)
In-Reply-To: <20070123163442.GA18662@elf.ucw.cz> (Pavel Machek's message of "Tue\, 23 Jan 2007 17\:34\:42 +0100")
Pavel Machek <pavel@ucw.cz> writes:
> But I still believe it can be out.
>
> Do you believe it could be a user-space daemon or what?
Yes, what prevents userspace daemon watching /dev/input/event* to
provide this functionality?
Well that was my first attempt. Just an hack, but it works. Nonetheless I found
the kernel-level approach fitting better the problem: it is elegant, simpler
and more efficient than user-level one.
For example, the subsystem provides at kernel-level handy
hiberante/suspend/resume callbacks that I use to turn on/off the timer,
avoiding the time-warp problem. Doing that at user-level would be far more
messy...
Bye
--
An age is called Dark not because the light fails to shine, but because people
refuse to see it. - James Michener, Space
next prev parent reply other threads:[~2007-01-23 17:11 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 19:29 [ANNOUNCE] System Inactivity Monitor v1.0 Alessandro Di Marco
2007-01-19 7:38 ` Arjan van de Ven
2007-01-19 14:49 ` Alessandro Di Marco
2007-01-19 17:45 ` Scott Preece
2007-01-19 22:21 ` Jan Engelhardt
2007-01-19 22:30 ` Scott Preece
2007-01-19 10:11 ` Pavel Machek
2007-01-21 21:04 ` Jan Engelhardt
2007-01-23 9:38 ` Pavel Machek
2007-01-22 12:46 ` Alessandro Di Marco
2007-01-23 9:41 ` Pavel Machek
2007-01-23 14:14 ` Alessandro Di Marco
2007-01-23 16:34 ` Pavel Machek
2007-01-23 17:11 ` Alessandro Di Marco [this message]
2007-01-23 18:44 ` Pavel Machek
2007-01-24 2:51 ` Alessandro Di Marco
2007-01-26 17:15 ` Pavel Machek
2007-01-26 17:55 ` Alessandro Di Marco
2007-01-27 17:45 ` Pavel Machek
2007-01-27 19:20 ` Vojtech Pavlik
2007-01-29 13:58 ` Alessandro Di Marco
2007-01-29 22:28 ` Pavel Machek
2007-01-29 22:42 ` Alessandro Di Marco
2007-01-30 0:03 ` Pavel Machek
2007-01-30 9:42 ` Vojtech Pavlik
2007-01-30 12:33 ` Alessandro Di Marco
2007-01-30 13:09 ` Vojtech Pavlik
2007-01-30 15:22 ` Alessandro Di Marco
2009-01-27 0:52 ` [PATCH] input: Activity counters Alessandro Di Marco
2009-01-27 0:54 ` Alessandro Di Marco
2009-01-27 0:54 ` Alessandro Di Marco
2009-01-27 0:54 ` Alessandro Di Marco
2007-01-29 8:24 ` [ANNOUNCE] System Inactivity Monitor v1.0 Stefan Seyfried
2007-01-24 18:08 ` Alessandro Di Marco
2007-01-23 19:01 ` Mattia Dongili
2007-01-23 19:02 ` Pavel Machek
2007-01-23 20:07 ` Mattia Dongili
2007-01-23 19:34 ` Scott Preece
2007-01-24 2:02 ` Alessandro Di Marco
2007-01-24 14:01 ` Pavel Machek
2007-01-19 21:18 ` Bill Davidsen
2007-01-20 15:37 ` Alessandro Di Marco
[not found] <7ELhf-4rC-9@gated-at.bofh.it>
[not found] ` <7FKM6-7Gy-1@gated-at.bofh.it>
[not found] ` <7G6ME-1g2-11@gated-at.bofh.it>
[not found] ` <7GqrZ-6YY-1@gated-at.bofh.it>
[not found] ` <7GuFj-5pj-5@gated-at.bofh.it>
[not found] ` <7GwQL-h3-7@gated-at.bofh.it>
[not found] ` <7GzF3-4L6-47@gated-at.bofh.it>
2007-01-25 12:28 ` Bodo Eggert
2007-01-25 15:18 ` Scott Preece
2007-01-25 15:43 ` Alessandro Di Marco
2007-01-25 16:03 ` Scott Preece
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lkjthdmd.fsf@gmx.it \
--to=dmr@gmx.it \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=vojtech@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.