Description of problem:
SSIA
Version-Release number of selected component (if applicable):
microcode_ctl-1.17-1.42.1.el6
How reproducible:
Always, apparently.
Steps to Reproduce:
1. watch boot messages, or run service microcode_ctl start
Actual results:
/etc/init.d/microcode_ctl: line 52: syntax error near unexpected token `}'
/etc/init.d/microcode_ctl: line 52: `}'
And cpu microcode isn't applied (!)
Expected results:
Quiet success :)
Additional info:
The cause of the error is this:
stop()
{
}
Please remember that functions in BASH can't have an empty body. If there's no command to run for this function in this init script, it should at least execute something like `true', or it shouldn't be defined at all and the 'case' branch for 'stop' should just run `exit 0'.
Looks like the fix actually landed in 1.17-2.el6 and I've confirmed this fix resolves the issue. Will close out once the package appears in an official compose.
Description of problem: SSIA Version-Release number of selected component (if applicable): microcode_ctl-1.17-1.42.1.el6 How reproducible: Always, apparently. Steps to Reproduce: 1. watch boot messages, or run service microcode_ctl start Actual results: /etc/init.d/microcode_ctl: line 52: syntax error near unexpected token `}' /etc/init.d/microcode_ctl: line 52: `}' And cpu microcode isn't applied (!) Expected results: Quiet success :) Additional info: The cause of the error is this: stop() { } Please remember that functions in BASH can't have an empty body. If there's no command to run for this function in this init script, it should at least execute something like `true', or it shouldn't be defined at all and the 'case' branch for 'stop' should just run `exit 0'.