Bug 699891 - WISHLIST: Allow specification of ks log file destination.
Summary: WISHLIST: Allow specification of ks log file destination.
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Provisioning
Version: 540
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: 260381
TreeView+ depends on / blocked
 
Reported: 2011-04-26 20:21 UTC by David Barr
Modified: 2015-09-11 15:02 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-09-11 15:02:28 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description David Barr 2011-04-26 20:21:18 UTC
+++ Description of problem:
Please update the kickstart configuration managers to allow specification of a path to the log files.

I have several RHNS-managed kickstart configurations. One %post script stopped working. I had trouble figuring out why. Part of my problem was that, after reboot, I could no longer see the output log file.

When %post script logging is selected, the scripts go in /root/<logfile>, as distinct from /mnt/sysimage/root/<logfile>. This means those log files are destroyed on reboot. Once I dropped the "reboot" keyword, I could go into /root and examine the logs.

+++ Version-Release number of selected component (if applicable):
5.4.0

+++ How reproducible:
Every time. I think this is normal behavior.

+++ Steps to Reproduce:
1. Boot from a kickstart file containing neither "shutdown" nor "reboot" keywords.
2. Compare the contents of /root and /mnt/sysimage/root
3. Note that files in /root are not expected to survive a reboot.
  
+++ Actual results:
Log files are saved in an unpreserved directory.

+++ Expected results:
Allow users to put the log files somewhere on sysimage.

+++ Additional info:

Thanks for an amazing product!


Note You need to log in before you can comment on or make changes to this bug.