Today there was a thread on cobbler-list:
https://fedorahosted.org/pipermail/cobbler/2008-August/000492.html
Not using --log, but in a 'functional' way.
Regards
Pablo
On Wed, 13 Aug 2008, Pat wrote:
Quote from the site http://kbase.redhat.com/faq/FAQ_42_10490.shtm:
============
%post nochroot --log=/tmp/post.log
//post scripts and commands go here
The logfiles will be saved in the temporary installation environment. In order to make them available when the installation is complete, they need to be copied to the installation environment in the %post section as show below. Note that this can not be done in a chrooted environment; the "nochroot" option must be used.
============
so when executing a chrooted %post script, it is not possible to log the activity? Is that right?
For example, I have a chrooted post section like this:
%post --log=/root/post.log
//do stuff
I tried that but the commands and resulting error messages (if any) were not logged with one exception. Within that post section, I did create a run once script which runs after the first reboot. The output from that script when it ran after the first reboot was recorded to the post.log which I don't quite understand. I'm glad I can see the output however I would like to see the results of the other post commands as well which were done after the OS install and before the first reboot.
BTW I'm using CentOS 5.0 and Redhat 5.2. Thanks for any help!
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
--
Pablo Iranzo Gómez
(http://Alufis35.uv.es/~iranzo/)
(PGPKey Available on http://www.uv.es/~iranzop/PGPKey.pgp)
--
Postulado de Boling sobre la Ley de Murphy:
Si se encuentra bien, no se preocupe. Se le pasará_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
