diff options
| author | Tom Gundersen <teg@jklm.no> | 2015-10-14 22:22:17 +0200 |
|---|---|---|
| committer | Sven Eden <yamakuzure@gmx.net> | 2017-04-26 12:58:55 +0200 |
| commit | fc157480fbf58337411532485f377afff5c794a1 (patch) | |
| tree | 989a19a23842d2c9d04b347f6360e2279b20e749 | |
| parent | dfbbceed38d59315271e2a7397c1f387a64c451b (diff) | |
login: suspend - be a bit more explicit when logging
When the Suspend method is called, the only log message we write
(unless debugging is enabled) is "Operation finished.". This is
not very helpful when trying to figure out what is going on, so
add what operation we are talking about to the message:
"Operation 'sleep' finished.".
Hat tip to Daniel Aleksandersen for pointing this out.
| -rw-r--r-- | src/login/logind-dbus.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/login/logind-dbus.c b/src/login/logind-dbus.c index 0c1f90dea..29f26f2db 100644 --- a/src/login/logind-dbus.c +++ b/src/login/logind-dbus.c @@ -2596,7 +2596,7 @@ int match_job_removed(sd_bus_message *message, void *userdata, sd_bus_error *err } if (m->action_job && streq(m->action_job, path)) { - log_info("Operation finished."); + log_info("Operation '%s' finished.", inhibit_what_to_string(m->action_what)); /* Tell people that they now may take a lock again */ send_prepare_for(m, m->action_what, false); |