summaryrefslogtreecommitdiff
path: root/TODO
AgeCommit message (Collapse)Author
2013-09-11core: failed scope units may not be restartedLennart Poettering
We don't allow reusing of scopes.
2013-09-11Update TODOLennart Poettering
2013-09-11fstab-generator: use DefaultDependencies=yesTom Gundersen
This removes some redundancy between the generator and the core mount handling.
2013-09-10service: remove pidfile after exit of a serviceLukas Nykryn
2013-09-09run: allow non-absolute paths as commandZbigniew Jędrzejewski-Szmek
2013-09-06TODO: update todoDave Reisner
2013-08-23"-" prefix for InaccessibleDirectories and ReadOnlyDirectoriesMaciej Wereski
2013-08-22remove hasprefix(), use startswith()Shawn Landden
2013-08-20Rename F_TYPE_CMP() to F_TYPE_EQUAL()Zbigniew Jędrzejewski-Szmek
2013-08-19man: fix spacing issue in systemd-nspawn(1)Zbigniew Jędrzejewski-Szmek
Same as 1e158d273.
2013-08-14README: update list of used LICENSEsKay Sievers
2013-08-13update TODOLennart Poettering
2013-08-13gpt-auto-generator: add basic auto-discovery of GPT partitionsLennart Poettering
This adds a simple generator that is capable of automatically discovering certain GPT partitions by their type UUID and mount/enable them. This currently covers swap partitions and /home partitions, but is expected to grow more features soon. This currently doesn't handle LUKS encrypted /home. This enables all swap partitions of type 0657fd6da4ab43c484e50933c84b4f4f, if found. This mounts the first partition of type 933ac7e12eb44f13b8440e14e2aef915 as /home, if it is found.
2013-08-13TODO: updateKay Sievers
2013-08-11logs-show: limit to 3 lines and use dots if not showing full messageZbigniew Jędrzejewski-Szmek
So far, we would show up to 128 bytes from a message, simply cutting of the rest. With multiline messages, it is quite common for a message to be longer than that, and this model doesn't really work anymore. A new limit is added: up to 3 lines will be shown, unless --full is used (c.f. first line below). The limit for bytes is extended to 300 bytes. An ellipsis will always be used, if some form of truncation occurs. If the tail of the message is cut off, either because of length or line limit, dots will be shown at the end of the last line. If this last line is short, the dots will be simply appended. If the last line is too long for that, it will be ellipsized with dots at the very end. Note that the limits are in bytes, not characters, and we suck at outputting unicode strings (c.f. last three lines below). Aug 11 10:46:21 fedora python[67]: test message line line... Aug 11 10:50:47 fedora python[76]: test message word word word word word word word word word word word wor... Aug 11 10:55:11 fedora python[83]: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx... Aug 11 11:03:21 fedora python[90]: ąąąąąąąąąąąąąąąąąąąąąąąąąąąąąą... Aug 11 11:03:53 fedora python[97]: aąąąąąąąąąąąąąąąąąąąąąąąąąąąąąą... Aug 11 11:25:45 fedora python[121]: aąąąąąąąąąąąąąąąąąąąąąąąąąąąąąąąąąą�...
2013-08-09update TODOLennart Poettering
2013-08-09service: prohibit Restart= set when Type=oneshotMaciej Wereski
2013-08-07TODO: add hwdb timestamp checkKay Sievers
2013-08-06TODO: add weird instance unit enable behaviorKay Sievers
2013-07-30update TODOLennart Poettering
2013-07-29update TODOLennart Poettering
2013-07-29update TODOLennart Poettering
2013-07-29update TODOLennart Poettering
2013-07-27TODO: remove kernel env var importing fixKay Sievers
2013-07-26logind: update the session state file before we send out the CreateSession() ↵Lennart Poettering
reply https://bugs.freedesktop.org/show_bug.cgi?id=67273
2013-07-26systemctl: move set-log-level to systemd-analyzeLennart Poettering
"systemctl set-log-level" is a command for analysis and tracing hence "systemd-analyze" should be the better home for it, thus allowing us to make the overly large "systemctl" a bit smaller.
2013-07-26systemctl: move "dump" command from systemctl to systemd-analyzeLennart Poettering
It's an analysis command and its format is explicitly not covered by any stability guarantees, hence move away from systemctl and into systemd-analyze, minimizing the already large interface of systemctl a bit. This patch also adds auto-paging to the various systemd-analyze commands where that makes sense
2013-07-24journal: immediately sync to disk as soon as we receieve an EMERG/ALERT/CRIT ↵Lennart Poettering
message
2013-07-22NEWS: prepare half a NEWS file for upcoming 206Lennart Poettering
2013-07-19man: update documentation of systemctl cgroup commandsLennart Poettering
2013-07-19man: update documentation of slice units a bitLennart Poettering
2013-07-19man: update scope unit man page a bitLennart Poettering
2013-07-19man: update pam_systemd documentation to current state of the codeLennart Poettering
2013-07-19man: list scope and slice units in systemd(1)Lennart Poettering
2013-07-19man: document sd_pid_get_slice() call of libsystemd-loginLennart Poettering
2013-07-19man: update systemd-nspawn regarding new --slice= logicLennart Poettering
2013-07-19man: drop the old cgroup settings from the man pagesLennart Poettering
2013-07-19core: add %v specifierZbigniew Jędrzejewski-Szmek
2013-07-19man: document Slice= setting (and other fixes)Lennart Poettering
2013-07-19update TODOLennart Poettering
2013-07-18TODO: updateKay Sievers
2013-07-17systemd,systemctl: export condition status and show failing conditionZbigniew Jędrzejewski-Szmek
$ systemctl --user status hoohoo hoohoo.service Loaded: loaded (/home/zbyszek/.config/systemd/user/hoohoo.service; static) Active: inactive (dead) start condition failed at Tue 2013-06-25 18:08:42 EDT; 1s ago ConditionPathExists=/tmp/hoo was not met Full information is exported over D-Bus: [(condition, trigger, negate, param, state),...] where state is one of "failed" (<0), "untested" (0), "OK" (>0). I've decided to use 0 for "untested", because it might be useful to differentiate different types of failure later on, without breaking compatibility. systemctl shows the failing condition, if there was a non-trigger failing condition, or says "none of the trigger conditions were met", because there're often many trigger conditions, and they must all fail for the condition to fail, so printing them all would consume a lot of space, and bring unnecessary attention to something that is quite low-level.
2013-07-18update TODOLennart Poettering
2013-07-16Update TODOZbigniew Jędrzejewski-Szmek
This point was done in 77a9e8de6.
2013-07-16journalctl: augment short mode with a cursor at the endZbigniew Jędrzejewski-Szmek
Two options are added: --show-cursor to print the cursor at the end, and --after-cursor to resume logs on the next line after the previous one.
2013-07-17update TODOLennart Poettering
2013-07-16updateLennart Poettering
2013-07-16rpm: add RPM macro for creating tmpfiles entries after package installationLennart Poettering
2013-07-16journal: return -ECHILD after a forkZbigniew Jędrzejewski-Szmek
A few asserts are replaced with 'return -EINVAL'. I think that assert should not be used to check argument in public functions. Fields in struct sd_journal are rearranged to make it less swiss-cheesy.
2013-07-16journalctl: Add support for showing messages from a previous bootJan Janssen
Hi, I redid the boot ID look up to use enumerate_unique. This is quite fast if the cache is warm but painfully slow if it isn't. It has a slight chance of returning the wrong order if realtime clock jumps around. This one has to do n searches for every boot ID there is plus a sort, so it depends heavily on cache hotness. This is in contrast to the other way of look-up through filtering by a MESSAGE_ID, which only needs about 1 seek + whatever amount of relative IDs you want to walk. I also have a linked-list + (in-place) mergesort version of this patch, which has pretty much the same runtime. But since this one is using libc sorting and armortized allocation, I prefer this one. To summarize: The MESSAGE_ID way is a *lot* faster but can be incomplete due to rotation, while the enumerate+sort will find every boot ID out there but will be painfully slow for large journals and cold caches. You choose :P Jan