10 More Discussions You Might Find Interesting
1. Red Hat
Hi Folks,
we are trying to install autosys4.5 on RHEL 7 Environment (Support to autosys 4.5 is stopped around 2014) but we are installing with extended approval.
need help on installing the application on the new enviornment from solaris. could someone please help or share me the installation... (0 Replies)
Discussion started by: somarbc
0 Replies
2. Red Hat
We are testing NFS Isilon mounts with autosys jobs. We continue to receive an autosys profile not found error. We have confirmed the profile file exists and can be referenced by the ID being used.
Autosys remote agent process is able to recognized and see the command section (command to be... (2 Replies)
Discussion started by: John Gillis
2 Replies
3. Shell Programming and Scripting
Hi Friends,
There is an Autosys scheduled job that runs on the second day of the month, and it is using the Business day calendar.
So when the month starts on a weekend or there is a holiday at the beginning of the month the second business day and second day of the month obviously do not... (1 Reply)
Discussion started by: Aditya_001
1 Replies
4. Infrastructure Monitoring
Hi guys . While installing the agent on an asset Solaris system:
root@system: /var/tmp/OC $ /opt/SUNWxvmoc/bin/agentadm configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65
agentadm: Version 12.1.2.2161 launched with args: configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65
Validating... (3 Replies)
Discussion started by: Junaid Subhani
3 Replies
5. AIX
We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys.
But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2
schedulers cannot exist in the same server.... (0 Replies)
Discussion started by: hidnana
0 Replies
6. UNIX and Linux Applications
We require Autosys remote agent to be installed in Unix (AIX) server to invoke a Unix script from Autosys.
But the issue is there is already a Jobtrac scheduler present in this server, and the support team who do Autosys installation say that these 2
schedulers cannot exist in the same server.... (0 Replies)
Discussion started by: hidnana
0 Replies
7. UNIX for Advanced & Expert Users
Hi,
I have one autosys job that will retrieve the proccess id's and will kill those processess as follows,
pid=`/usr/ucb/ps -auwwxx | grep MAIN |nawk '{print $2}'`
kill -9 pid
but after executing this particular job, its status is showing as TE(terminated) and the kill process is... (3 Replies)
Discussion started by: Kattoor
3 Replies
8. UNIX for Advanced & Expert Users
Hi Guys..
This is Mahesh..
Actually I have to work with autosys...
Can anyone tell me how to start Autosys in the command prompt of Linux(fedora 8)?
And from where can i download autosys software (2 Replies)
Discussion started by: mraghunandanan
2 Replies
9. UNIX for Advanced & Expert Users
moved to Solaris...
https://www.unix.com/sun-solaris/84558-installation-entirely-remote-solaris.html (0 Replies)
Discussion started by: vbe
0 Replies
10. AIX
Hi All,
I have the following 2 questions:
I can't seem to find which versions of VIOserver are supported by IBM.
and
if there are rule for installation of tooling (e.g. monitoring agents) on a VIOserver.
thanx in advance
>Raba (3 Replies)
Discussion started by: raba
3 Replies
SSH-COPY-ID(1) BSD General Commands Manual SSH-COPY-ID(1)
NAME
ssh-copy-id -- use locally available keys to authorise logins on a remote machine
SYNOPSIS
ssh-copy-id [-f] [-n] [-i [identity_file]] [-p port] [-o ssh_option] [user@]hostname
ssh-copy-id -h | -?
DESCRIPTION
ssh-copy-id is a script that uses ssh(1) to log into a remote machine (presumably using a login password, so password authentication should
be enabled, unless you've done some clever use of multiple identities). It assembles a list of one or more fingerprints (as described below)
and tries to log in with each key, to see if any of them are already installed (of course, if you are not using ssh-agent(1) this may result
in you being repeatedly prompted for pass-phrases). It then assembles a list of those that failed to log in, and using ssh, enables logins
with those keys on the remote server. By default it adds the keys by appending them to the remote user's ~/.ssh/authorized_keys (creating
the file, and directory, if necessary). It is also capable of detecting if the remote system is a NetScreen, and using its 'set ssh pka-dsa
key ...' command instead.
The options are as follows:
-i identity_file
Use only the key(s) contained in identity_file (rather than looking for identities via ssh-add(1) or in the default_ID_file). If the
filename does not end in .pub this is added. If the filename is omitted, the default_ID_file is used.
Note that this can be used to ensure that the keys copied have the comment one prefers and/or extra options applied, by ensuring that
the key file has these set as preferred before the copy is attempted.
-f Forced mode: doesn't check if the keys are present on the remote server. This means that it does not need the private key. Of
course, this can result in more than one copy of the key being installed on the remote system.
-n do a dry-run. Instead of installing keys on the remote system simply prints the key(s) that would have been installed.
-h, -? Print Usage summary
-p port, -o ssh_option
These two options are simply passed through untouched, along with their argument, to allow one to set the port or other ssh(1)
options, respectively.
Rather than specifying these as command line options, it is often better to use (per-host) settings in ssh(1)'s configuration file:
ssh_config(5).
Default behaviour without -i, is to check if 'ssh-add -L' provides any output, and if so those keys are used. Note that this results in the
comment on the key being the filename that was given to ssh-add(1) when the key was loaded into your ssh-agent(1) rather than the comment
contained in that file, which is a bit of a shame. Otherwise, if ssh-add(1) provides no keys contents of the default_ID_file will be used.
The default_ID_file is the most recent file that matches: ~/.ssh/id*.pub, (excluding those that match ~/.ssh/*-cert.pub) so if you create a
key that is not the one you want ssh-copy-id to use, just use touch(1) on your preferred key's .pub file to reinstate it as the most recent.
EXAMPLES
If you have already installed keys from one system on a lot of remote hosts, and you then create a new key, on a new client machine, say, it
can be difficult to keep track of which systems on which you've installed the new key. One way of dealing with this is to load both the new
key and old key(s) into your ssh-agent(1). Load the new key first, without the -c option, then load one or more old keys into the agent,
possibly by ssh-ing to the client machine that has that old key, using the -A option to allow agent forwarding:
user@newclient$ ssh-add
user@newclient$ ssh -A old.client
user@oldl$ ssh-add -c
... prompt for pass-phrase ...
user@old$ logoff
user@newclient$ ssh someserver
now, if the new key is installed on the server, you'll be allowed in unprompted, whereas if you only have the old key(s) enabled, you'll be
asked for confirmation, which is your cue to log back out and run
user@newclient$ ssh-copy-id -i someserver
The reason you might want to specify the -i option in this case is to ensure that the comment on the installed key is the one from the .pub
file, rather than just the filename that was loaded into you agent. It also ensures that only the id you intended is installed, rather than
all the keys that you have in your ssh-agent(1). Of course, you can specify another id, or use the contents of the ssh-agent(1) as you pre-
fer.
Having mentioned ssh-add(1)'s -c option, you might consider using this whenever using agent forwarding to avoid your key being hijacked, but
it is much better to instead use ssh(1)'s ProxyCommand and -W option, to bounce through remote servers while always doing direct end-to-end
authentication. This way the middle hop(s) don't get access to your ssh-agent(1). A web search for 'ssh proxycommand nc' should prove
enlightening (N.B. the modern approach is to use the -W option, rather than nc(1)).
SEE ALSO
ssh(1), ssh-agent(1), sshd(8)
BSD
June 17, 2010 BSD