10-12-2009
Does anybody has any idea?
6 More Discussions You Might Find Interesting
1. Red Hat
Hello;
I have 2 node Redhat Cluster (RHEL4 U4 and Cluster Suite) I'm using mc_data fiber channel switch for fencing
when I want to fence manually using
fence_mcdata -a x.x.x. -l xxx -p xxxx -n 5 -o disable
following messages appears
fencing node "test1"
agent "fence_mcdata" reports:... (0 Replies)
Discussion started by: sakir19
0 Replies
2. High Performance Computing
Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris.
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
3. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
4. Red Hat
I have 2 VM's setup with a shared VMware disk running RHEL 7.1 (just updated to 7.2 with yum update), and would like to know what is the easiest Fence device to implement for testing purposes. Apparently, I need a fence device before my IP resources will come online.
I have the cluster... (1 Reply)
Discussion started by: mrmurdock
1 Replies
5. Solaris
I build up two node cluster (node1, node2) in virtualbox. For these two nodes I add 5 shared disk. (Also each node have own OS disk).
1 shared disk for vtoc
2 shared disk for NFS resource group
2 shared disk for WEB resource group
When I finished my work; two nodes was ok and shared disk... (4 Replies)
Discussion started by: sonofsunra
4 Replies
6. Solaris
Greetings!
Will be firing up the good ole pizza box, soon. Does anyone know if Solaris 7 is still okay to use? Last time I attempted was 2006.
Thank you in advance,
ControlTomato (6 Replies)
Discussion started by: ControlTomato
6 Replies
LEARN ABOUT DEBIAN
gendsa
GENDSA(1SSL) OpenSSL GENDSA(1SSL)
NAME
gendsa - generate a DSA private key from a set of parameters
SYNOPSIS
openssl gendsa [-out filename] [-des] [-des3] [-idea] [-rand file(s)] [-engine id] [paramfile]
DESCRIPTION
The gendsa command generates a DSA private key from a DSA parameter file (which will be typically generated by the openssl dsaparam
command).
OPTIONS
-des|-des3|-idea
These options encrypt the private key with the DES, triple DES, or the IDEA ciphers respectively before outputting it. A pass phrase is
prompted for. If none of these options is specified no encryption is used.
-rand file(s)
a file or files containing random data used to seed the random number generator, or an EGD socket (see RAND_egd(3)). Multiple files
can be specified separated by a OS-dependent character. The separator is ; for MS-Windows, , for OpenVMS, and : for all others.
-engine id
specifying an engine (by its unique id string) will cause gendsa to attempt to obtain a functional reference to the specified engine,
thus initialising it if needed. The engine will then be set as the default for all available algorithms.
paramfile
This option specifies the DSA parameter file to use. The parameters in this file determine the size of the private key. DSA parameters
can be generated and examined using the openssl dsaparam command.
NOTES
DSA key generation is little more than random number generation so it is much quicker that RSA key generation for example.
SEE ALSO
dsaparam(1), dsa(1), genrsa(1), rsa(1)
1.0.1e 2013-02-11 GENDSA(1SSL)