![]() | |||||||||||||
Messages in this thread |
In message <Pine.LNX.4.58.0402030418310.22596@devserv.devel.redhat.com> you write:
> > introduce a SIGRECONF (default ignored). But AFAICT, introducing a new
> > signal isn't possible (at least on x86) without breaking glibc.> > you can introduce a variable RT signal for this purpose no problem - and
> one would want to have a queued signal for this anyway. Ie. by default the
> notification is disabled, but a new syscall sets up the process to be
> notified of CPU up/down events, on a signal # picked by the app. But this
> this indeed is dbus domain ...
Yeah, this workaround because we can't add a new signal isn't very
good, though ("I can't add a new signal, so you choose!"). In
practice, it sucks for libraries and it sucks for children.
As you point out, DBUS is a better solution anyway. Of course,
proposing that something which doesn't yet exist will solve all our
problems is usually a sign of laziness or optimism 8).
Cheers,
Rusty.
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
| ||||||||||||
| Last update: 2005-03-22 14:00 [W:0.260 / U:0.280 seconds] ©2003-2008 Jasper Spaans | |||||||||||||