hi all, gpfs.base 4.2.1-0 rpm has following postuninstall snippet
it will disable the gpfs unit always (when previously enabled), whether this is a removal or an upgrade. this however prevents an update to 4.2.1-1, as it will remove the unit that is added during install (post has 'systemctl reenable /usr/lpp/mmfs/lib/systemd/gpfs.service') so after the upgrade, we are left with nodes that have no gpfs service unit (and thus no gpfs). it would have been better if the rpm symlinked teh service to the /usr/lib/systemd/... units, and enabled/disabled it. i'll probably rpmrebuild the 4.2.1-1 rpms to make a more permanent unit in a proper system location. other tips are welcome. stijn > postuninstall scriptlet (using /bin/sh): > if test -n "$DEBUG" || test -n "$DEBUGpostun"; then > set -x > fi > packageCnt=$1 > debian_release="/etc/debian_version" > > # set the system utilities if they are in different path on different > systems > if [ -f "$debian_release" ] > then > AWK=/usr/bin/awk > else > AWK=/bin/awk > fi > > if /usr/bin/systemctl -q is-enabled gpfs.service 2>/dev/null > then > /usr/bin/systemctl -q disable gpfs.service > fi > _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at spectrumscale.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss
