DBUS features

My examples are going to be somewhat bad, but please see through them
for the reasoning and the necessity of these features.
1) We need a way to know if someone, using DBUS, is logged in either in
a
terminal or an X session.
Think of a situation where you have a piece of software that needs to do
tasks from time to time (changing of runlevels is likely).
You want to automate this, or at least be able to tell the machine to do
it. However, this process should wait (or the shell script that does all
the running) until no one is logged in. Yes, yes, who and w might
provide that, but I find this a cleaner solution.
2) We need a way to know if some critical process, such as up2date, is
being run at shutdown and allow the app, as long as it response every X
amount of time (2 minutes or so) to continue to run.
Think of a network environment and someone is doing an up2date via cron
or ssh. Someone finishes using the computer and turns it off. This
should pause, in a test or graphical shut down, showing a list of such
processes. It should not execute any shut down sequences until this list
is empty, or they programs all cease to respond.
These processes should notify DBUS, that they need to complete and that
they have completed, and have an event handler to respond to DBUS.
I have a few ideas about the VNC features as well, but those will come
later.
What do you all think? Is this possible (I am fairly sure it is)? Is it
a good thing... I think so?
Trever Adams
P.S. In the thread where I used HAL in the place of DBUS, someone
pointed out #1 is probably fairly simple, and the tone made it sound
that it may not be a good idea in FC, this is fine if it is the case,
but the functionality and core pieces for #2 should still be looked at.
--
"Walking on water and developing software to specification are easy as
long as both are frozen." --Edward V. Berard