diff options
| author | Olivier Brunel <i.am.jack.mail@gmail.com> | 2012-11-05 00:28:45 +0100 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2012-11-15 15:59:39 +0100 |
| commit | f09a7d25545b5e3a2dd3dfc1ff7ebc8560a3354c (patch) | |
| tree | 595f5e8a9b63fdb3d9f5a60cd1a989fc8b0f38a4 /src/core/transaction.c | |
| parent | 45c0c61df3c63cb1f20505c8d292385d5e300578 (diff) | |
systemd: highlight ordering cycle deletions
Having unit(s) removed/not started, even if it solved the issue and allowed
to boot successfully, should still be considered an error, as something
clearly isn't right.
This patch elevates the log message from warning to error, and adds a status
message to make things more obvious.
Diffstat (limited to 'src/core/transaction.c')
| -rw-r--r-- | src/core/transaction.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/core/transaction.c b/src/core/transaction.c index 4bce942012..ee6992a81a 100644 --- a/src/core/transaction.c +++ b/src/core/transaction.c @@ -374,7 +374,8 @@ static int transaction_verify_order_one(Transaction *tr, Job *j, Job *from, unsi if (delete) { - log_warning("Breaking ordering cycle by deleting job %s/%s", delete->unit->id, job_type_to_string(delete->type)); + log_error("Breaking ordering cycle by deleting job %s/%s", delete->unit->id, job_type_to_string(delete->type)); + status_printf(ANSI_HIGHLIGHT_RED_ON " SKIP " ANSI_HIGHLIGHT_OFF, true, "Ordering cycle found, skip %s", unit_description(delete->unit)); transaction_delete_unit(tr, delete->unit); return -EAGAIN; } |