diff options
| author | Lennart Poettering <lennart@poettering.net> | 2017-09-20 18:29:08 +0200 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2017-09-22 15:24:55 +0200 |
| commit | 646cc98dc81c4d0edbc1b57e7bca0f474b47e270 (patch) | |
| tree | cb1cb46e7f34666615746413641c9e8e9593d9f1 /src | |
| parent | documentation: document nss-systemd's internal environment variables in ENVIR... (diff) | |
| download | systemd-646cc98dc81c4d0edbc1b57e7bca0f474b47e270.tar.xz systemd-646cc98dc81c4d0edbc1b57e7bca0f474b47e270.zip | |
job: change result field for log message about job result RESULT= → JOB_RESULT=
So, currently, some of the structured log messages we generated based on
jobs carry the result in RESULT=, and others in JOB_RESULT=. Let's
streamline this, as stick to JOB_RESULT= in one place.
This is kind of an API break, but given that currently most software has
to check both fields anyway, I think we can get away with it.
Why unify on JOB_RESULT= rather than RESULT=? Well, we manage different
types of result codes in systemd. Most importanlty besides job results
there are also service results, and we should be explicit in what we
mean here.
Diffstat (limited to 'src')
| -rw-r--r-- | src/core/job.c | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/src/core/job.c b/src/core/job.c index dd0733030c..f04c8a2168 100644 --- a/src/core/job.c +++ b/src/core/job.c @@ -806,7 +806,8 @@ static void job_log_status_message(Unit *u, JobType t, JobResult result) { default: log_struct(job_result_log_level[result], LOG_MESSAGE("%s", buf), - "RESULT=%s", job_result_to_string(result), + "JOB_TYPE=%s", job_type_to_string(t), + "JOB_RESULT=%s", job_result_to_string(result), LOG_UNIT_ID(u), LOG_UNIT_INVOCATION_ID(u), NULL); @@ -815,7 +816,8 @@ static void job_log_status_message(Unit *u, JobType t, JobResult result) { log_struct(job_result_log_level[result], LOG_MESSAGE("%s", buf), - "RESULT=%s", job_result_to_string(result), + "JOB_TYPE=%s", job_type_to_string(t), + "JOB_RESULT=%s", job_result_to_string(result), LOG_UNIT_ID(u), LOG_UNIT_INVOCATION_ID(u), mid, @@ -823,6 +825,7 @@ static void job_log_status_message(Unit *u, JobType t, JobResult result) { } static void job_emit_status_message(Unit *u, JobType t, JobResult result) { + assert(u); /* No message if the job did not actually do anything due to failed condition. */ if (t == JOB_START && result == JOB_DONE && !u->condition_result) @@ -905,7 +908,7 @@ int job_finish_and_invalidate(Job *j, JobResult result, bool recursive, bool alr * the unit itself. We don't treat JOB_CANCELED as failure in * this context. And JOB_FAILURE is already handled by the * unit itself. */ - if (result == JOB_TIMEOUT || result == JOB_DEPENDENCY) { + if (IN_SET(result, JOB_TIMEOUT, JOB_DEPENDENCY)) { log_struct(LOG_NOTICE, "JOB_TYPE=%s", job_type_to_string(t), "JOB_RESULT=%s", job_result_to_string(result), |