Bug 338541 - %post --log does not work as expected
Summary: %post --log does not work as expected
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-18 18:38 UTC by Lubomir Kundrak
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-10-26 14:31:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Lubomir Kundrak 2007-10-18 18:38:25 UTC
Description of problem:

I did put the following line in my kickstart file:

  %post --log=/root/post.log

After the installation, the file /root/post.log does not exist at all, though my
post script generates a fairly big amount of output on both stdout and stderr.

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

anaconda-0:11.3.0.42-1.i386

Comment 1 Chris Lumens 2007-10-18 19:14:25 UTC
When you say "after the installation", are you referring to after you have
rebooted and are looking at the installed system, or are you referring to after
anaconda has finished but before you have rebooted?

Comment 2 Lubomir Kundrak 2007-10-18 20:39:08 UTC
Chris: after the reboot. I have not looked right after anaconda finished. Isn't
it expected to be in the target filesystem after the reboot?

Comment 3 Chris Lumens 2007-10-26 14:31:52 UTC
Oh I see what's going on here.  The log file location isn't being interpreted
relative to the chroot, so your logs are ending up in /root instead of
/mnt/sysimage/root and are therefore being destroyed when you reboot.  This
should be fixed in the next build of anaconda.


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