summaryrefslogtreecommitdiff
path: root/TODO
AgeCommit message (Collapse)Author
2014-01-22bus: temporarily disable faking of seclabels, as this is broken in kdbus ↵Lennart Poettering
right now
2014-01-20TODO: updateKay Sievers
2014-01-20update TODOLennart Poettering
2014-01-20update TODOLennart Poettering
2014-01-18sd-resolve: rename get_next() and get_n_queries() + cleanupDaniel Buch
2014-01-18sd-resolve: get rid of sd_resolve_freeanswer()Daniel Buch
2014-01-17Update TODOLennart Poettering
2014-01-17update TODOLennart Poettering
2014-01-13libsystemd-bus: rename to libsystemdTom Gundersen
Documentation was updated to refer to either 'libsystemd' or 'sd-bus' in place of libsystemd-bus.
2014-01-13TODO: updateKay Sievers
2014-01-12TODO: update rtnl/network sectionsTom Gundersen
2014-01-12update TODOLennart Poettering
2014-01-11man: add busctl(1)Zbigniew Jędrzejewski-Szmek
2014-01-08networkd: use structured logging for links and bridgesZbigniew Jędrzejewski-Szmek
2014-01-08Improve messages about user mode a bitZbigniew Jędrzejewski-Szmek
2014-01-08update TODOLennart Poettering
2014-01-07update TODOLennart Poettering
2014-01-05TODO: extend login capability noteDavid Herrmann
We cannot remove CAP_SYS_ADMIN, which basically makes removing all other capabilities useless. Anyhow, still wouldn't hurt checking whether stuff like CAP_KILL can be dropped from logind.
2013-12-27bus: add some preliminary docs for porting existing dbus1 client libraries ↵Lennart Poettering
to kdbus
2013-12-25man: document fail/nofail, auto/noautoZbigniew Jędrzejewski-Szmek
Also s/filesystem/file system/ in a few places.
2013-12-25Trim TODOZbigniew Jędrzejewski-Szmek
2013-12-26update TODOLennart Poettering
2013-12-24update TODOLennart Poettering
2013-12-23update TODOLennart Poettering
2013-12-22update TODOLennart Poettering
2013-12-22bus: introduce concept of "const" propertiesLennart Poettering
This way we have four kinds of properties: a) those which are constant as long as an object exists b) those which can change and PropertiesChange messages with contents are generated c) those which can change and where the PropertesChange merely includes invalidation d) those which can change but for which no events are generated Clients (through code generators run on the introspection XML) can thus aggressively cache a, b, c, with only d excluded.
2013-12-21util: remove union dirent_storageFlorian Weimer
2013-12-21update TODOLennart Poettering
2013-12-21update TODOLennart Poettering
2013-12-21update TODOLennart Poettering
2013-12-19driverd: implement AddMatch/RemoveMatch logicLennart Poettering
2013-12-18libudev: disable monitor inside a containerKay Sievers
Uevents are events of the host, which should not leak into a container. Containers do not support hotplug at the moment, and devices and uevents are not namespace aware.
2013-12-18libudev: devices received from udev are always initializedKay Sievers
2013-12-18comment out udev's is_initialized call until the problem is sorted outKay Sievers
2013-12-17update TODOLennart Poettering
2013-12-16update TODOLennart Poettering
2013-12-13update TODOLennart Poettering
2013-12-13man: document more error codes for sd_bus_request_name()Lennart Poettering
2013-12-13update TODOLennart Poettering
2013-12-13event: when unreffing an event source from its own handler, detach fd from epollLennart Poettering
The pattern of unreffing an IO event source and then closing its fd is frequently seen in even source callbacks. Previously this likely resultet in us removing the fd from the epoll after it was closed which is problematic, since while we were dispatching we always kept an extra reference to event source objects because we might still need it later.
2013-12-13event: rework sd-event exit logicLennart Poettering
With this change a failing event source handler will not cause the entire event loop to fail. Instead, we just disable the specific event source, log a message at debug level and go on. This also introduces a new concept of "exit code" which can be stored in the event loop and is returned by sd_event_loop(). We also rename "quit" to "exit" everywhere else. Altogether this should make things more robus and keep errors local while still providing a way to return event loop errors in a clear way.
2013-12-12update TODOLennart Poettering
2013-12-12bus: properly generate NameOwnerChanged messages when we take from/give back ↵Lennart Poettering
to queue/starter
2013-12-12update TODOLennart Poettering
2013-12-11journal: add ability to browse journals of running OS containersLennart Poettering
This adds the new library call sd_journal_open_container() and a new "-M" switch to journalctl. Particular care is taken that journalctl's "-b" switch resolves to the current boot ID of the container, not the host.
2013-12-11journald: port to sd-event and enable watchdog supportLennart Poettering
2013-12-11event: hook up sd-event with the service watchdog logicLennart Poettering
Adds a new call sd_event_set_watchdog() that can be used to hook up the event loop with the watchdog supervision logic of systemd. If enabled and $WATCHDOG_USEC is set the event loop will ping the invoking systemd daemon right after coming back from epoll_wait() but not more often than $WATCHDOG_USEC/4. The epoll_wait() will sleep no longer than $WATCHDOG_USEC/4*3, to make sure the service manager is called in time. This means that setting WatchdogSec= in a .service file and calling sd_event_set_watchdog() in your daemon is enough to hook it up with the watchdog logic.
2013-12-11event: when handling SIGCHLD of a child process only reap after dispatching ↵Lennart Poettering
event source That way the even source callback is run with the zombie process still around so that it can access /proc/$PID/ and similar, and so that it can be sure that the PID has not been reused yet.
2013-12-10update TODOLennart Poettering
2013-12-10bus: introduce "trusted" bus concept and encode access control in object vtablesLennart Poettering
Introduces a new concept of "trusted" vs. "untrusted" busses. For the latter libsystemd-bus will automatically do per-method access control, for the former all access is automatically granted. Per-method access control is encoded in the vtables: by default all methods are only accessible to privileged clients. If the SD_BUS_VTABLE_UNPRIVILEGED flag is set for a method it is accessible to unprivileged clients too. By default whether a client is privileged is determined via checking for its CAP_SYS_ADMIN capability, but this can be altered via the SD_BUS_VTABLE_CAPABILITY() macro that can be ORed into the flags field of the method. Writable properties are also subject to SD_BUS_VTABLE_UNPRIVILEGED and SD_BUS_VTABLE_CAPABILITY() for controlling write access to them. Note however that read access is unrestricted, as PropertiesChanged messages might send out the values anyway as an unrestricted broadcast. By default the system bus is set to "untrusted" and the user bus is "trusted" since per-method access control on the latter is unnecessary. On dbus1 busses we check the UID of the caller rather than the configured capability since the capability cannot be determined without race. On kdbus the capability is checked if possible from the attached meta-data of a message and otherwise queried from the sending peer. This also decorates the vtables of the various daemons we ship with these flags.