Another option, without actually removing the newline, but printing without it:
(in your command, date is running on the local host, which may or may not be the same as the remote host, you'd need add quotes to change that)
Hi guys,
I am trying to do a ssh for performing a set of actions.
Find it below:
I need to put the user/ kernel/ DISTRO variables before I complete this operation.
what I observed is when ever I put a `command` in those quotes, it performs thta action in local system rather than remote one.... (5 Replies)
Hello sir,
Im using ubuntu distro.
We all know that ssh is used for password less entry.So, I have the public key and the IP address and the username thats it. Now to login it to the system either I should have password or a private key.Now I have the blacklist of private/public keys. But I dont... (1 Reply)
i have a bash script on serverA, when i run the script on the server, it runs fine. the way to run the script is like this ./script "option1"
Now i am trying to call it from local laptop using ssh command, my command is as the following
ssh serverA ~/script "option1"
and i got error... (7 Replies)
Hi all,
Scenario - trying to run a batch job on a second machine.
DIR=directory
user=user
server=server
Here is what i have- ssh user@server 'sleep2; cd $DIR; <jobname>'
I have got access to the correct directory, i checked with a pwd command previous.
Problem is the job i... (1 Reply)
Hi,
i have a shellscript, where in i need to connect to different server start these three jobs and exit from the server and start the same three jobs on local server.
ssh user@remotehost 'bash -s' << EOF
${GETT_HOME}/bin/start1 &
sleep 10
${GETT_HOME}/bin/start2 &
sleep 10... (1 Reply)
Hi, I've an issue in a shell script:
I'm opening an ssh connection to a remote server, then I want to store the result of a ls command in a variable, but it doesn't work: the ls is done on the local machine.
ssh user@server << EOF
ls # works as expected (ls is done remotely)
test=`ls` # the... (1 Reply)
How should i make the following code working
#!/bin/bash
INPUTFILE="test.txt"
while read STRING; do
IP=`host -t A $STRING | awk '{print $NF}'`
HOSTNAME=`ssh -oPasswordAuthentication=no -oStrictHostKeyChecking=no $IP "hostname"`
echo $HOSTNAME > out.txt
done < $INPUTFILE
At this moment while... (3 Replies)
Hello i am having an issue with bash script and this is the code
now=$(cat hosts1.txt | awk '{print $2;}')
while read n ;do
ssh root@$now 'useradd test1; echo -e "test1\ntest1" | passwd test1 && echo "test1 ALL=(ALL:ALL) ALL" >> /etc/sudoers'
When i execute only part with cat, it... (8 Replies)
I have a variable called $a1 which maps to something like "http://servername proxy1 count http" and a lots of entries in a file on remote server.
If I have the following in my .sh script:
sed -i "\%$a1%d" mylog.txtthe line is deleted from mylog.txt. Great.
I'm trying now to remvoe this from a... (3 Replies)
Discussion started by: say170
3 Replies
LEARN ABOUT OSF1
hosts.equiv
hosts.equiv(4) Kernel Interfaces Manual hosts.equiv(4)NAME
hosts.equiv - A file containing the names of remote systems and users that can execute commands on the local system
SYNOPSIS
/etc/hosts.equiv
DESCRIPTION
The /etc/hosts.equiv file and the .rhosts file in a user's home directory contain the names of remote hosts and users that are equivalent
to the local host or user. An equivalent host or user is allowed to access a local nonsuperuser account with the rsh command or rcp com-
mand, or to log in to such an account without having to supply a password.
The /etc/hosts.equiv file specifies equivalence for an entire system, while a user's .rhosts file specifies equivalence between that user
and remote users. The local user and the target system exist in the same area as the hosts.equiv file. The .rhosts file must be owned by
the user in whose home directory the file is located, or by the superuser. It cannot be a symbolic link.
Each line, or entry, in hosts.equiv or .rhosts may consist of the following: A blank line. A comment (begins with a #). A host name (a
string of any printable characters except newline, #, or white space). In addition, an NIS netgroup can be specified in place of the host
name. A host name followed by white space and a user name. In addition, an NIS netgroup can be specified in place of the host name, user
name, or both. A single plus (+) character. This means any host and user. The keyword NO_PLUS. This keyword disallows the use of the plus
character (+) to match any host or user on a system-wide basis. By default, the line containing this keyword is a comment. Remove the com-
ment character to disallow the use of the plus character.
Entries in the hosts.equiv file are either positive or negative. Positive entries allow access; negative entries deny access. The following
entries are positive: host name user name +@netgroup
In addition, the plus sign (+) can be used in place of the host name or user name. In place of the host name, it means any remote host. In
place of the user name, it means any user.
The following entries are negative: -host name -user name -@netgroup
To be allowed access or denied access, a user's remote host name and user name must match an entry in hosts.equiv or .rhosts. The
hosts.equiv file is searched first; if a match is found, the search ends. Therefore, the order in which the positive and negative entries
appear is important. If a match is not found, .rhosts is searched if it exists in the user's home directory.
A host name or user name can match an entry in hosts.equiv in one of the following ways: The official host name (not an alias) of the
remote host matches a host name in hosts.equiv. The remote user name matches a user name in hosts.equiv. If a user name parameter is
included in the hosts.equiv file, this means that the remote user is a trusted user and is allowed to rlogin to any local user account
without being prompted for a password. Otherwise, if the user name parameter is not specified in the hosts.equiv file, the name of the
remote user must match that of the local user. If the remote user name does not match a user name in hosts.equiv, the remote user name
matches the local user name.
CAUTIONS
For security purposes, the files /etc/hosts.equiv and .rhosts should exist and be readable and writable only by the owner, even if they are
empty.
EXAMPLES
The following are sample entries in an /etc/hosts.equiv file: # Allows access to users on host1 and host2 that have accounts on this host:
host1 host2 # Allows access to user johnson on host1 to any local user: host1 johnson # Allows access to all users on systems specified in
netgroup chicago +@chicago # Denies access to users specified in netgroup finance on host5 host5 -@finance # Allows access to all users on
all systems except root + -root
RELATED INFORMATION
Commands: rcp(1), rlogin(1), rsh(1)
Functions: ruserok(3).
Files: netgroup(4)
Daemons: rlogind(8), rshd(8) delim off
hosts.equiv(4)