Michael J McCafferty wrote: > All, > I am trying to automate our standard build of RHEL3. I have built a ks.cfg > file that specifies the packages, contains the network confiugration, the > partitions, etc. All of those work... when I run the kickstart installation > the > config in the ks.cfg file is the resulting configration of the new system. > Great ! > The problem is that the post-installation commands in the %post area of the > ks.cfg are not run. How does one troiubleshoot where thee %post commands are > barfing ? There is nothing in /var/log/messages, anaconda.ks.cfg, install.log, > or install.log.syslog. > The anaconda.ks.cfg does not contain my %post commands that are in the > ks.cfg > that I used for installation of the new system. > > Thoughts ?
add a ``set -x'' right after your %post You may also want to add: exec > /var/log/kickstart_post.log exec 2>&1 -john -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
