Created attachment 918510 [details]
kickstart file with %post script
Description of problem:
During a kickstart %post script (without --nochroot option) a log file is created in the non-chrooted filesystem that is empty even if the script produces output.
Version-Release number of selected component (if applicable): rhel7GA
How reproducible: always
Steps to Reproduce:
1. start kickstart installation with a %post script that produces output
2. cat logfile in /tmp corresponding to post script in /mnt/sysimage/tmp
Empty log file
Log file containing output of %post script
Check /var/log/anaconda/ on the target system. Is it there?
Once installation is complete the post script logs show up in /var/log/anaconda/ on the target system. While the scripts are running there is no corresponding log file on the target system. The ks-script-xxx log in /tmp also remains empty while the scripts are running.
That is as expected, because of buffering the output may not be written to the files immediately.
Development Management has reviewed and declined this request.
You may appeal this decision by reopening this request.