summaryrefslogtreecommitdiff
path: root/src/core/dbus-path.c
diff options
context:
space:
mode:
authorFranck Bui <fbui@suse.com>2016-11-07 17:14:59 +0100
committerFranck Bui <fbui@suse.com>2016-11-17 18:16:49 +0100
commit3c670f8998a34e99f0981622f57350b974448887 (patch)
tree2582fe452bbd205b96c1049466e32489716f1706 /src/core/dbus-path.c
parent2bcc330942d526b6004a67c92e284ad842bd5e59 (diff)
core: reprint the question every 2 sec in ask_char()
ask_char() now reprints the question every 2sec automatically. It prefixes its output with '\r' to to bring the cursor to the beginning of the terminal line, and then print the message, redoing it every 2sec. As long as nothing interferes with out output this logic will have no visible effect as we constantly overprint the visible text with the exact same text. However, if something is dumped in the middle, then our question won't get lost, as we'll ask soon again. This is useful if the question is asked to a terminal that is also used to dump some other status messages/logs. For example when confirmation messages are enabled during the boot (systemd.confirm_spawn=1), the question can easily be lost if the kernel logs are also enabled and both use the same console. Idea suggested by Lennart Poettering.
Diffstat (limited to 'src/core/dbus-path.c')
0 files changed, 0 insertions, 0 deletions