Sponsored Content
Operating Systems AIX [Tip] FS-Manipulation in 7.1.3-Clusters Post 302952350 by bakunin on Tuesday 18th of August 2015 06:44:40 AM
Old 08-18-2015
Quote:
Originally Posted by agent.kgb
bakunin is right. The command imfs is not documented. The redbook is the only documentation about a lot of intermediate-level LVM commands and it is very outdated. There are some other undocumented and very useful commands in the redbook, such as ipl_varyon, getlvodm or lvlstmajor. IBM doesn't like if you know too much about AIX internals ;-)
This is absolutely true!

It might be a worthwile community project to write documentation for these undocumented commands. getlvodm, for instance, i have used literally for decades now (it must have been introduced in AIX 4.1.x or so). Anybody interested?

bakunin

@Scrutinizer: i took agent.kgbs link as a rather witty comeback regarding my use of the word "undocumented". No harm done. ;-))
 

8 More Discussions You Might Find Interesting

1. High Performance Computing

question about clusters

hello all...first off let me say hi and im really glad to be apart of this community....tried to join awhile back but i couldnt for some reason im a highschool student and im eager to learn and what im trying to learn now is clusters i have 3 computers in my room all connected on a simple hub ... (1 Reply)
Discussion started by: hexadecimal0011
1 Replies

2. Solaris

about Solaris Patch Clusters md5sum

Hi, for Solaris Patch Clusters version 10_x86_Recommended.zip (Jul 15 2009 / 817 MB - SunSolve) MD5: be40488b0fb1d081deda69dbca415be3 is correct? (the problem is that I don't have an account. ...therefore I can't login on Sunsolve for view MD5 page) yes, is a terrible thread! ... (3 Replies)
Discussion started by: gxmsgx
3 Replies

3. Solaris

meaning of states in sun clusters

Hi Everybody, As I am new to Sun Clusters, Please help me what is "online but not monitored" state of resources and "online - service is online" in status message. Thank you. (1 Reply)
Discussion started by: mayahari
1 Replies

4. Solaris

jumpstart install clusters

Hello, I'm trying to jumpstart a machine with Solaris 10, however the disks in my machine are only 18GB, but I want to have all the developer packages but none of the X windows stuff that can be quite large. Wondered if it was possible to somehow get a list of all packages and remove the ones... (4 Replies)
Discussion started by: Actuator
4 Replies

5. Solaris

VCS Clusters

:)Hi, can someone please explain VCS clustering and where do we need VCS clusters ..? :o:)Thanks in advance :o:) (1 Reply)
Discussion started by: amitbisht9
1 Replies

6. High Performance Computing

I/O bound computing clusters

I want to build a computing cluster and have been looking into grid solutions. My understanding from grid solutions is that participating nodes have to actually sign up to participate in a computation and that an isolated piece of work is sent to the node through a request from that node (pull).... (4 Replies)
Discussion started by: figaro
4 Replies

7. Red Hat

How to configure redhat clusters on VMWARE?

I'm using redhat 5.1 installed on VMware work station9. Can you guys help me to configure redhat clusters. (1 Reply)
Discussion started by: karthik9358
1 Replies

8. Shell Programming and Scripting

Getting unique based on clusters

Hi, I have a file with 25 clusters and each cluster has multiple rows. I need to find the unique genes in each cluster and assign them Annotation Cluster 2 Enrichment Score: 10.199579524507685 Category Term Count % PValue Genes List Total Pop Hits Pop Total Fold... (1 Reply)
Discussion started by: Diya123
1 Replies
SSH-AGENT(1)						    BSD General Commands Manual 					      SSH-AGENT(1)

NAME
ssh-agent -- authentication agent SYNOPSIS
ssh-agent [-c | -s] [-d] [-a bind_address] [-t life] [command [arg ...]] ssh-agent [-c | -s] -k DESCRIPTION
ssh-agent is a program to hold private keys used for public key authentication (RSA, DSA). The idea is that ssh-agent is started in the beginning of an X-session or a login session, and all other windows or programs are started as clients to the ssh-agent program. Through use of environment variables the agent can be located and automatically used for authentication when logging in to other machines using ssh(1). The options are as follows: -a bind_address Bind the agent to the UNIX-domain socket bind_address. The default is /tmp/ssh-XXXXXXXXXX/agent.<ppid>. -c Generate C-shell commands on stdout. This is the default if SHELL looks like it's a csh style of shell. -d Debug mode. When this option is specified ssh-agent will not fork. -k Kill the current agent (given by the SSH_AGENT_PID environment variable). -s Generate Bourne shell commands on stdout. This is the default if SHELL does not look like it's a csh style of shell. -t life Set a default value for the maximum lifetime of identities added to the agent. The lifetime may be specified in seconds or in a time format specified in sshd_config(5). A lifetime specified for an identity with ssh-add(1) overrides this value. Without this option the default maximum lifetime is forever. If a commandline is given, this is executed as a subprocess of the agent. When the command dies, so does the agent. The agent initially does not have any private keys. Keys are added using ssh-add(1). When executed without arguments, ssh-add(1) adds the files ~/.ssh/id_rsa, ~/.ssh/id_dsa and ~/.ssh/identity. If the identity has a passphrase, ssh-add(1) asks for the passphrase on the terminal if it has one or from a small X11 program if running under X11. If neither of these is the case then the authentication will fail. It then sends the identity to the agent. Several identities can be stored in the agent; the agent can automatically use any of these identities. ssh-add -l displays the identities currently held by the agent. The idea is that the agent is run in the user's local PC, laptop, or terminal. Authentication data need not be stored on any other machine, and authentication passphrases never go over the network. However, the connection to the agent is forwarded over SSH remote logins, and the user can thus use the privileges given by the identities anywhere in the network in a secure way. There are two main ways to get an agent set up: The first is that the agent starts a new subcommand into which some environment variables are exported, eg ssh-agent xterm &. The second is that the agent prints the needed shell commands (either sh(1) or csh(1) syntax can be gener- ated) which can be evaluated in the calling shell, eg eval `ssh-agent -s` for Bourne-type shells such as sh(1) or ksh(1) and eval `ssh-agent -c` for csh(1) and derivatives. Later ssh(1) looks at these variables and uses them to establish a connection to the agent. The agent will never send a private key over its request channel. Instead, operations that require a private key will be performed by the agent, and the result will be returned to the requester. This way, private keys are not exposed to clients using the agent. A UNIX-domain socket is created and the name of this socket is stored in the SSH_AUTH_SOCK environment variable. The socket is made accessi- ble only to the current user. This method is easily abused by root or another instance of the same user. The SSH_AGENT_PID environment variable holds the agent's process ID. The agent exits automatically when the command given on the command line terminates. FILES
~/.ssh/identity Contains the protocol version 1 RSA authentication identity of the user. ~/.ssh/id_dsa Contains the protocol version 2 DSA authentication identity of the user. ~/.ssh/id_rsa Contains the protocol version 2 RSA authentication identity of the user. /tmp/ssh-XXXXXXXXXX/agent.<ppid> UNIX-domain sockets used to contain the connection to the authentication agent. These sockets should only be readable by the owner. The sockets should get automatically removed when the agent exits. SEE ALSO
ssh(1), ssh-add(1), ssh-keygen(1), sshd(8) AUTHORS
OpenSSH is a derivative of the original and free ssh 1.2.12 release by Tatu Ylonen. Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos, Theo de Raadt and Dug Song removed many bugs, re-added newer features and created OpenSSH. Markus Friedl contributed the support for SSH protocol versions 1.5 and 2.0. BSD
January 17, 2010 BSD
All times are GMT -4. The time now is 05:49 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy