grep: /etc/init/plymouth-shutdown.override: No such file or directory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
Fix Released
|
Medium
|
Dimitri John Ledkov | ||
Trusty |
Fix Released
|
Medium
|
Dimitri John Ledkov |
Bug Description
[Impact]
* Unnecessary bogus harmless messages printed to the user in the default configuration.
[Test Case]
* Execute wait-for-state against any job that does not have an override
* Make sure no log / grep error messages from not finding .override file are printed for the wait-for-state job
[Regression Potential]
* minimal output from $ grep, was already suppressed with '-q', now the stderr is redirected as well, exit / result from grep is checked.
[Other Info]
* Original bug report:
I'm using Ubuntu 14.04 dev with plymouth 0.8.8-0ubuntu15 and on every boot I'm seeing another line of the warning "grep: /etc/init/
Related branches
description: | updated |
Changed in upstart (Ubuntu): | |
importance: | Undecided → Medium |
assignee: | nobody → Dimitri John Ledkov (xnox) |
Changed in upstart (Ubuntu Trusty): | |
status: | Triaged → Fix Committed |
There are no upstart scripts in the official plymouth package that grep /etc/init/ plymouth- shutdown. override. This looks like a local bug. Where does this grep happen?