On 08/05/2009 11:42 PM, Larry Brigman wrote:
On Wed, Aug 5, 2009 at 7:40 AM, Jeroen van Meeuwen<kanarip@xxxxxxxxxxx> wrote:
On Wed, 5 Aug 2009 07:34:42 -0700, Larry Brigman<larry.brigman@xxxxxxxxx>
wrote:
Because the timestamp file in the future prevents new configurations from
being
recognized as up to date. If I had a way to force the time during the
%pre script to
UTC, this would not be an issue.
You mean your configuration management utility (if any) compares by
timestamp rather then, say, md5sum? You're not using Puppet/CFEngine/BCFG?
Not using Puppet/CFEngine/BCFG.
The timestamp file is created during the post install of the rpm.
This is used as a safety
check to insure that the configuration tool is run after install to
have an up to date configuration
with the existing config management utility - sanity check of the config file.
Right, and although that seems a but hackerish, in %post, you can
ntpdate <server>; touch /path/to/timestamp-file, no? You wouldn't really
need to adjust the installer images for that purpose, you just need to
make sure the appropriate ntp/ntpdate package is installed.
-- Jeroen
_______________________________________________
Kickstart-list mailing list
Kickstart-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/kickstart-list
