Martin Langhoff (martin.langhoff@xxxxxxxxx) said: > An excellent counterexample is incrond - I pass 'events' to scripts > using incrond's hooks into inotify. The scripts themselves are not > running, I only have one tiny tiny daemon listening. I can rig it to > handle thousands of specific different events and scripts, and still > the footprint is small (and if I monitor directories smartly, it > doesn't need to burden the kernel much either). Honestly, they're different usage cases. dbus is for exposing services and objects through a simple IPC interface - if you're exposing an object, you sort of need a backing for it. It honestly sounds like you're using incrond for something that would fit into upstart's usage model. Bill -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
