summaryrefslogtreecommitdiffstats
path: root/base/root/scripts
diff options
context:
space:
mode:
authorMartin Schwenke <martin@meltin.net>2009-05-25 16:02:45 +1000
committerMartin Schwenke <martin@meltin.net>2009-05-25 16:02:45 +1000
commitbb89ab08c4f17309698b357c1b5f3a2c66e6964e (patch)
tree3a3124332e6fa944ad97beac5dde6cbaf60c9762 /base/root/scripts
parent18750152023c23ab7f9e91be96878bb90ddeb6e9 (diff)
Rationalise the the use of "yum clean all" in postinstall scripts.
Using "yum clean all" before doing a "yum update" seems to avoid certain weird problems. We were doing a clean before an update in both the basic postinstall (which is always present) and the SoFS-postinstall. However, this wasn't avoiding problems when a base image was being used for some other purpose. The current thinking is to put a clean after the update in the basic postinstall - so this is the last thing that happens when a base is created without the SoFS-postinstall. This should mean that, when a node is created using the base, any updates will need to fetch fresh repo data... so the update should be clean. Signed-off-by: Martin Schwenke <martin@meltin.net>
Diffstat (limited to 'base/root/scripts')
-rwxr-xr-xbase/root/scripts/SoFS-postinstall.sh1
1 files changed, 0 insertions, 1 deletions
diff --git a/base/root/scripts/SoFS-postinstall.sh b/base/root/scripts/SoFS-postinstall.sh
index e043d39..159154a 100755
--- a/base/root/scripts/SoFS-postinstall.sh
+++ b/base/root/scripts/SoFS-postinstall.sh
@@ -5,7 +5,6 @@
# basic-postinstall.sh but we may have just rewound the cluster, so we
# might be running this on the node install of from kickstart.
echo "Updating from YUM repositories"
-yum clean all
yum -y update
echo "Trying install of scsi-target-utils"