Red Hat Bugzilla – Bug 338541
%post --log does not work as expected
Last modified: 2007-11-30 17:12:18 EST
Description of problem:
I did put the following line in my kickstart file:
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):
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?
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?
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.