This is my problem: I'm installing RT (Request Tracker) when I found the firsts difficulties with package that must be configured. I could resolve them . The real problem are the missing dependencies. The command perl -MCPAN -e"install denpendency" resolved some missing modules. See it.
Please, I need to resolve this problem ASAP.
Thanks
Last edited by pludi; 07-09-2010 at 01:56 AM..
Reason: code tags, please...
Hi,
On what factors does the cksum depend.
If i build 2 machines exactly the same, then can i get the checksum of 2 compiled files same.
Thanks (3 Replies)
Question: What do you do when you have a software dependency conflict?
Case in point, according to Freeware for Solaris, before one can install
tcl, tk must be installed first. And then when I go to investigate dependencies for tk, it says that tcl must be installed first!!!
Its like... (2 Replies)
Hi,
I have scheduled two jobs, 2nd job is depend upon the 1st one.
Once the 1st job will finish the execution , then only 2nd job will start execution.
Both the jobs present in the cron file.
Please reply as earleist because this is one my requirement, where should put the condition,... (1 Reply)
Dear Friends ,
I am using RHEL 5 server . In Linux when I am going to install 'mod_ssl' rpm then I got the following error :
# rpm -ivh mod_ssl-2.2.3-6.el5.i386.rpm --aid --force
warning: mod_ssl-2.2.3-6.el5.i386.rpm: Header V3 DSA signature: NOKEY, key ID 37017186
error: Failed... (5 Replies)
Hi,
I'm having issues with implicit dependencies for my RPM package. This is the error I'm getting:
error: Failed dependencies:
libclntsh.so.11.1()(64bit) is needed by geomatica-10.4-0.x86_64
Our software has a dynamically loaded library which links to the Oracle's libclntsh.so.11.1... (2 Replies)
rsync is having dependencies - libpopt, libiconv, libintl and libgcc
rsync need to be distributed to different machines and this is forcing to make sure these dependencies available in those machines.
Is there any way to copy rsync alone? Can I follow static linking ? (1 Reply)
Hi all,
i'm trying to upgrade pandorafms to the new version 4.0.3-130118,
actually i have installed on my machine the version 3.0.0-8.1.el5,
the error i'm getting when trying to update its the following
rpm -Uvh pandorafms_agent_unix-4.0.3-130118.noarch.rpm
error: Failed dependencies:
... (1 Reply)
I'm trying to package the latest Oracle JDK (1.7.0_51) into an RPM. Packaging works fine but when i try to install via rpm -Uvh xxx.rpm, i get the following:
#sudo rpm -ivh Sun_JDK7-1.7.0-51.x86_64.rpm
error: Failed dependencies:
libavcodec.so.52()(64bit) is needed by Sun_JDK7-1.7.0-51.x86_64... (3 Replies)
Hi guys
when I'm trying to install some RPMs file I got this errors
# rpm -ivh DSM-IBMAIXServer-7.2-796075.noarch.rpm
error: failed dependencies:
perl(Digest::MD5) is needed by DSM-IBMAIXServer-7.2-796075
perl(Exporter) is needed by DSM-IBMAIXServer-7.2-796075
... (1 Reply)
Discussion started by: khaled_ly84
1 Replies
LEARN ABOUT HPUX
cmhaltpkg
cmhaltpkg(1m)cmhaltpkg(1m)NAME
cmhaltpkg - halt a high availability package
SYNOPSIS
cmhaltpkg [-v] [-t] [-n node_name]... package_name...
cmhaltpkg [-v] [-s] [-n node_name]... package_name...
DESCRIPTION
cmhaltpkg connects to the Serviceguard cluster manager and halts the specified package(s) or multi-node package instance(s).
When a package or package instance is halted, global switching (AUTO_RUN) is disabled for that package.
cmhaltpkg may be run on any node within the cluster and may operate on any package within the cluster.
To halt a package, a user must either be a superuser with effective user ID of zero (see id(1) and su(1)), or have an access policy of
PACKAGE_ADMIN allowed in the cluster or package configuration file. See access policy in cmquerycl(1m) or cmmakepkg(1m).
If no node_name arguments are supplied, each package will be halted on any and all nodes where it is running. If the package is not running
on any nodes, the command will fail.
cmhaltpkg should not be used to halt SYSTEM_MULTI_NODE packages (HP-UX only). Use cmhaltnode or cmhaltcl to halt SYSTEM_MULTI_NODE packages
instead. Packages of other types may be halted on a subset of the configured nodes by specifying one or more node_name arguments.
cmhaltpkg will fail if each specified package is not running on all the specified nodes.
Packages are halted in the order required by their configured dependencies. Packages without configured dependencies are halted in the
order specified on the command line. To successfully halt a package, all required dependent packages must either be previously halted or
specified as a package_name argument in the cmhaltpkg command. Packages configured with STORAGE_GROUP are implicitly dependent on the cor-
responding multi-node cluster volume manager (CVM) package. (HP-UX only)
cmhaltpkg validates its command line prior to halting any package and returns an error if the user does not have correct access to complete
the operation or if illegal combinations of node_name and package_name arguments are encountered.
If a problem is detected while halting a package, cmhaltpkg exits with an error indication and remaining package_name arguments are not
processed.
A package in maintenance mode that was start up to and including a specified module can be halted from that specified module. Only those
modules which were started are halted.
Options
cmhaltpkg supports the following options:
-n node_name Acts only on a specific node. If the package is not running on the specified node, it will not be halted.
-v Verbose output will be displayed.
-t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or pack-
ages. This option validates the node's eligibility with respect to the package dependencies as well as the external
dependencies such as EMS resources, package subnets, and storage before predicting any package placement decisions.
This option is not legal for package in maintenance mode.
-s Symmetric halt is only for packages in maintenance mode. If a package in maintenance mode has been started up to a
module as specified by cmrunpkg -m, then cmhaltpkg -s will halt the package up to that module. Otherwise, cmhaltpkg
-s will halt the package for all the modules specified in its configuration file.
RETURN VALUE
cmhaltpkg returns the following value:
0 Successful completion.
1 Command failed.
2 Command failed due to a transient condition.
EXAMPLES
A sequence of cmhaltpkg and cmrunpkg commands may be used to move a package from one node to another. For example, the package may be
halted on one node and then run on a new node, provided that the package is enabled for the new node.
To move package package1 to node node2, do the following:
cmhaltpkg package1
cmrunpkg -n node2 package1
cmmodpkg -e package1 (to enable package switching, if desired)
AUTHOR
cmhaltpkg was developed by HP.
SEE ALSO cmmakepkg(1m), cmquerycl(1m), cmmodpkg(1m), cmrunpkg(1m), cmviewcl(1m), cmeval(1m).
Requires Optional Serviceguard Software cmhaltpkg(1m)