On Wed, Oct 22, 2014 at 06:47:47PM +0200, Martin Kolman wrote:
Add an Initial Setup specific log handling module that forwards nicely formated log messages to the system log and also correctly maps message log levels to system log priorities (in journalctl: info & debug - no highlight, warning - bold, error & critical - red).
This finally makes it possible to report in detail what's going on during the Initial Setup run, with emphasis on providing enough information on problematic areas, such as Kickstart parsing.
BTW, to check for all Initial Setup log messages in Journal you can use the -u flag with the Initial Setup unit name:
journalctl -u initial-setup-graphical
or
journalctl -u initial-setup-text
Resolves: rhbz#1153768 Signed-off-by: Martin Kolman mkolman@redhat.com
initial_setup/__main__.py | 49 ++++++++++++++++++++++++++++++++++--- initial_setup/gui/spokes/eula.py | 9 +++++++ initial_setup/initial_setup_log.py | 50 ++++++++++++++++++++++++++++++++++++++ initial_setup/product.py | 5 +++- initial_setup/tui/spokes/eula.py | 8 ++++++ 5 files changed, 116 insertions(+), 5 deletions(-) create mode 100644 initial_setup/initial_setup_log.py
Ack