01-19-2007
Both (Solaris 10 & AIX) systems are production system. I am not able to give the output's of the /etc/hosts & $HOME/.rhosts files, because the customer is not ready to provide with the information. The only thing which is bothering me is that I am able to get the remote shell.....so why the remote shell commands are not working directly from Solaris10..???
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi,
a little help.
I need to test the return code of a list file command on a remote system (Unix) using the rsh command. More exactly, to test is a directory exists, I try the following command:
rsh $remoteHost "ls -la " $DirRemote
Now, if the $DirRemote is not correct and I test... (3 Replies)
Discussion started by: gio123bg
3 Replies
2. Programming
Hi,
How I can get system function executed command return value ? I want to know mv command success or not ?
#include <stdio.h>
main()
{
int ret;
ret = system( "mv x.dat y.dat" );
printf( "system ret:\n", ret );
} (3 Replies)
Discussion started by: haiudhaya
3 Replies
3. UNIX for Dummies Questions & Answers
Hi there again,
Running Solaris 10 with built-in Java. Seems to compile and run fine.
Problem is: Say I want to see contents of current directory. In a shell, I'd just write "ls" and it outputs the content.
When I write a Java file, I have the following line:
System.out.println("ls");
... (1 Reply)
Discussion started by: EugeneG
1 Replies
4. Solaris
Hi all,
Kind of an emergency situation, I have to NFS mount an AIX filesystem on to a Sun Solaris OS (5.10).
Typically from Sun to Sun is:
mount -F nfs <remote file system>/dir <mount point>
Which of course doesn't work if the remote file system is another OS (like AIX).
Is there... (1 Reply)
Discussion started by: jeffpas
1 Replies
5. Shell Programming and Scripting
hello All,
I need to invoke by perl script some program/command and monitor it for 5
minutes . In case it still running for more then 5 min I need to send a signal which will stop it.
I implemeted this as shown below by using eval & alarm
and I'd like to know if there is a better way to... (1 Reply)
Discussion started by: Alalush
1 Replies
6. AIX
Hey Guyz,
I am preparing an inventory kindof thing about the aix servers.. I need help to find out the below details for many AIX servers..
Machine model and version
Disk Size
RAM size
no. of CPUs and thier information
list of softwares installed
I searched in web.. but not much info I... (4 Replies)
Discussion started by: thariqueakbar
4 Replies
7. Solaris
Hi,
we have server, that is auditing actions executed, and then sends them to the syslog server.
But there is arguments to issued to the commands in the audit trail, but there is no such arguments in the syslog output on the syslog server!
Example - I executed:
# ls -la
audit... (1 Reply)
Discussion started by: masloff
1 Replies
8. Shell Programming and Scripting
:wall:i'm system administrator. now i have a trouble. i want to fetch the command which the login users performed by shell.but i don't know how to process this problem.if anyone tell me how to do this work I would be very grateful.thank you! (4 Replies)
Discussion started by: anline5104
4 Replies
9. HP-UX
Hi all
I wonder if its possible to mount on a hp-ux server a file system that was previously mounted on a solaris 10 server. The LUN is on NetApp stoarge.
The problem on hp-ux I cannot do pvcreate on the lun (disk) because contains data.
Any help will be appreciated
FR (2 Replies)
Discussion started by: fretagi
2 Replies
10. AIX
I have a following requirement in production
system 1 : LINUX
User: abcd
system 2: AIX (it is hosting a production DB)
Requirement
user abcd from system 1 should have read access on archive log files created by DB on system 2. The log files are created with permissions 540 by user ora ,... (2 Replies)
Discussion started by: amitnm1106
2 Replies
LEARN ABOUT OSX
hosts.equiv
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
hostname [username]
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, +@netgroup (from which
only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, +@netgroup (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
user name.
+@anetgroup username
The user username may login to the local host from any machine listed in the netgroup anetgroup.
+
+ +
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
WARNINGS
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
FILES
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO
rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)
HISTORY
The .rhosts file format appeared in 4.2BSD.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD