Bugfixes:
-* Should systemctl status \* work on all unit types, not just .service?
-
-* Dangling symlinks of .automount unit files in .wants/ directories, set up
- automount points even when the original .automount file did not exist
- anymore. Only the .mount unit was still around.
-
-* ExecStart with unicode characters fails in strv_split_extract:
+* the error paths in usbffs_dispatch_ep() leak memory
- [Service]
- Environment=ONE='one' "TWO='two two' too" THREE=
- ExecStart=/bin/python3 -c 'import sys;print(sys.argv)' $ONE $TWO $THREE
+* copy.c: set the right chattrs before copying files and others after
External:
* Rearrange tests so that the various test-xyz.c match a specific src/basic/xyz.c again
-Features:
+* copy.c: set the right chattrs before copying files and others after
-* add O_TMPFILE support to copy_file_atomic()
+* rework mount.c and swap.c to follow proper state enumeration/deserialization
+ semantics, like we do for device.c now
-* nspawn: greater control over selinux label?
+Features:
-* sd-event: implement inotify events, as we can safely and robustly do that now
- for any inode without fearing confusion by inodes appearing at multiple
- places: we can open it with O_PATH first, then store its inode in a hash
- table, to recognize duplicate watches before creating (and thus corrupting
- pre-existing ones) them, and using /proc/self/fd/ to add it right after.
+* When reloading configuration PID 1 should reset all its properties to the
+ original defaults before calling parse_config()
-* the error paths in usbffs_dispatch_ep() leak memory
+* Add OnTimezoneChange= and OnTimeChange= stanzas to .timer units in order to
+ schedule events based on time and timezone changes.
+
+* nspawn: greater control over selinux label?
* cgroups: figure out if we can somehow communicate in a cleaner way whether a
elogind instance not running in the cgroup root shall or shall not manage the
numbers.
* port systemctl, elogind-inhibit, busctl, … over to format-table.[ch]'s table formatters
+* Check that users of inotify's IN_DELETE_SELF flag are using it properly, as
+ usually IN_ATTRIB is the right way to watch deleted files, as the former only
+ fires when a file is actually removed from disk, i.e. the link count drops to
+ zero and is not open anymore, while the latter happens when a file is
+ unlinked from any dir.
+
* pid1: lock image configured with RootDirectory=/RootImage= using the usual nspawn semantics while the unit is up