diff options
| author | Martin Schwenke <martin@meltin.net> | 2009-05-25 16:02:45 +1000 |
|---|---|---|
| committer | Martin Schwenke <martin@meltin.net> | 2009-05-25 16:02:45 +1000 |
| commit | bb89ab08c4f17309698b357c1b5f3a2c66e6964e (patch) | |
| tree | 3a3124332e6fa944ad97beac5dde6cbaf60c9762 /base/root/scripts/nsd_server_common.bash | |
| parent | 18750152023c23ab7f9e91be96878bb90ddeb6e9 (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/nsd_server_common.bash')
0 files changed, 0 insertions, 0 deletions
