PatchingGroupWiseOnLinux

From CoolSolutionsWiki

Search

Views

> my other wikis

Goal Be able to quickly apply GroupWise patches and back out of them IF Necessary.

1 Methodology
2 Process

[edit]

Methodology

I like to have a Plan A and a Plan B.

Plan A: tar/zip up the directory where the binary and configuration files are. So one can go back IF Needed .
Plan B: Be able to keep the RPM Database accurate (binary on the file system matches what is in the RPM Database).

[edit]

Process

[edit]

BACKING UP AGENTS:

/etc/init.d/grpwise stop
cd /opt/novell/groupwise/
tar -cvf agents_numberOFCurrentVer.tar agents I decided I like to get everything in agents, this include the bin (binary) and the share (configuration files).
mkdir numberOFCurrentVer
mv agents_numberOFCurrentVer.tar numberOFCurrentVer
tar -xvf agents_numberOFCurrentVer.tar observe the unpack'd bin directory of agent code

[edit]

Installing the new code

Please note That you should have the same code base, on the SAME box. So, if this box is running a MTA and GWIA, make sure you apply BOTH. If this box has MTA/POA/GWIA, makes sure you apply all of those RPMs.

I use yast2 from SSH because the rpm -i seems to complain about newer/older versions. yast2 sw_single allows one to slamein the binary.

yast2 sw_single novell-groupwise-gwia-7.0.2-20070125.i386.rpm
yast2 sw_single novell-groupwise-agents-7.0.2-20070125.i386.rpm
ast2 sw_single novell-groupwise-gwha-7.0.2-20070125.i386.rpm

[edit]

Backout Plan A

I prefer Plan B, because your RPM Database is accurate. You have not done a hack job of the binary files.

So, lets assume you want to go with Plan A.

I would copy the .tar file into a backup directory and then untar it. (tar -xvf see above). Then you can chose to copy the binary (/opt/novell/grpwise/agents/bin) and or your configuration files (in the /opt/novell/grpwise/agents/share directory).

[edit]