diff options
author | Lennart Poettering <lennart@poettering.net> | 2018-10-06 18:43:28 +0200 |
---|---|---|
committer | Lennart Poettering <lennart@poettering.net> | 2018-11-09 17:08:59 +0100 |
commit | c4e48030cf299b56668b1cd360c4ec93e7f97b20 (patch) | |
tree | 0e428d49887fe74216ad7da03b8af5318d2ad601 /TODO | |
parent | e5c36295d81971ef75d9c6f98f0890b92a4a353f (diff) | |
download | systemd-c4e48030cf299b56668b1cd360c4ec93e7f97b20.tar.gz systemd-c4e48030cf299b56668b1cd360c4ec93e7f97b20.tar.bz2 systemd-c4e48030cf299b56668b1cd360c4ec93e7f97b20.zip |
sd-bus: make "close+flush-on-exit" optional when using sd-event with sd-bus
This adds a new pair of API calls sd_bus_set_close_on_exit() and
sd_bus_get_close_on_exit(). They control whether an sd_bus object
attached to a an sd-event loop shall automatically be flushed/closed
when the event loop goes down. Usually that's a good thing, except for
very few cases where the bus connection is longer living than the event
loop it is attached on. Specifically, this is the case for nspawn, where
we run the event loop only while the container is up, but afterwards
still want to be able to use the bus connection.
Diffstat (limited to 'TODO')
0 files changed, 0 insertions, 0 deletions