01-08-2008
Service Guard 11.16 in HPUX 11.11?
Hello!
I need to upgrade my Service Guard 11.14 to 11.16, but I don't know how to do it. We have two HP9000 running on HPUX 11.11.
Where can i download the ServiceGuard 11.16?
Is there any manual or website where i can read the steps to follow?
Thanks in advance!
7 More Discussions You Might Find Interesting
1. HP-UX
Can somebody please give me a description of MC Service Guard running on HP Unix? (3 Replies)
Discussion started by: czinzi
3 Replies
2. HP-UX
Hi admins,
I need some help writing functional specifications for planning a two nodes Service Guard Cluster.
Can anybody help me
thanks at advance (1 Reply)
Discussion started by: hmaiida
1 Replies
3. Shell Programming and Scripting
I am running HPUX and using WLM (workload manager). I want to write a script to fork CPUs to basically take CPUs from other servers to show that the communication is working and CPU licensing is working. Basically, I want to build a script that will use up CPU on a server. Any ideas? (2 Replies)
Discussion started by: cpolikowsky
2 Replies
4. HP-UX
I'm sharing this in case anybody needs it. Modified from the original solaris pwage script. This modified hpux script will check /etc/password file on hpux trusted systems search /tcb and grep the required u_succhg field. Calculate days to expiry and notify users via email.
original solaris... (2 Replies)
Discussion started by: sparcguy
2 Replies
5. Red Hat
HI All,
I am using RHEL 5.0 32 Bit, i was trying to install HP Service Guard Cluster in my machine where i installed RHEL5. The problem is that when i am running cmquery -n selva -C mycluster.ascii. Its output is that LICENSE FILE NOT FOUND, so exiting.
So i have tried so many things. Pls... (1 Reply)
Discussion started by: skumar7466
1 Replies
6. HP-UX
Hi There
I have a 2 node failover SG cluster, with a 4 packages running, that due to various reason I cant fail over/test for a while.
Therefore have created a test package to test over the 2 nodes. The package resources include a presented LUN from our HP SAN and a package IP address. The... (2 Replies)
Discussion started by: Pentat0nicc
2 Replies
7. HP-UX
Hi ,
I have added a new logical volume on 11.16 service guard cluster on hpux server version 11.11, Need a confirmation if the configuration changes will be applicable with only running cmapplyconf or would the cluster services need to restarted ?
I tried searching the manual, but was not... (0 Replies)
Discussion started by: kpatel786
0 Replies
LEARN ABOUT XFREE86
dh_systemd_start
DH_SYSTEMD_START(1) Debhelper DH_SYSTEMD_START(1)
NAME
dh_systemd_start - start/stop/restart systemd unit files
SYNOPSIS
dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]
DESCRIPTION
dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
sysv init script is available.
As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
which case it will only be restarted after the upgrade). This logic is not used when there is a corresponding SysV init script because
invoke-rc.d performs the stop/start/restart in that case.
OPTIONS
--restart-after-upgrade
Do not stop the unit file until after the package upgrade has been completed. This is the default behaviour in compat 10.
In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.
This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
will not get confused by the package being upgraded while it's running before using this option.
--no-restart-after-upgrade
Undo a previous --restart-after-upgrade (or the default of compat 10). If no other options are given, this will cause the service to
be stopped in the prerm script and started again in the postinst script.
-r, --no-stop-on-upgrade, --no-restart-on-upgrade
Do not stop service on upgrade.
--no-start
Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
corresponding init script).
NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.
Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.
SEE ALSO
debhelper(7)
AUTHORS
pkg-systemd-maintainers@lists.alioth.debian.org
11.1.6ubuntu2 2018-05-10 DH_SYSTEMD_START(1)