10 More Discussions You Might Find Interesting
1. Solaris
i am facing an issue that the server give a connection timeout after 60 sec for any request more than that number . i tried to increase the TCP INTERVAL TIMEOUT from the default 60000 ms to more higher number.
the server seems to work fine and didn't give me the massage of the timeout but the... (0 Replies)
Discussion started by: core99
0 Replies
2. Shell Programming and Scripting
Hi,
In a file, I have to mark duplicate records as 'D' and the latest record alone as 'C'.
In the below file, I have to identify if duplicate records are there or not based on Man_ID, Man_DT, Ship_ID and I have to mark the record with latest Ship_DT as "C" and other as "D" (I have to create... (7 Replies)
Discussion started by: machomaddy
7 Replies
3. Shell Programming and Scripting
I've a Centralized Server which can connect to all Oracle Databases.
When I was trying the below code it doesn't work, But tnsping was working fine.
#!D:/perl5/bin/perl.exe
use DBI;
my $dbh = DBI->connect('dbi:Oracle:QBDIWCE', 'IDUSER', 'SECRET123#' ) || die( $DBI::errstr . "\n" ) ;
... (1 Reply)
Discussion started by: ilugopal
1 Replies
4. Shell Programming and Scripting
Hi All.
I have a script, in which its throwing me error like
/data/ds/dpr_ebicm_uat//etl/cm3_0/entities/BBME/parameters/cm_file_util.plg: line 7: export: `exist.=SQL1024N A database connection does not exist. SQLSTATE=08003': not a valid identifier
whereas i have already made a... (4 Replies)
Discussion started by: vee_789
4 Replies
5. UNIX for Dummies Questions & Answers
Hi
I when I trying to SFTP a file to a server I am getting this below error:
Connecting to 3.12.911.100...
ssh_askpass: exec(/usr/lib/ssh/ssh-askpass): No such file or directory
Host key verification failed.
Connection closed
Can you please help me in debugging this error.
... (3 Replies)
Discussion started by: krishna87
3 Replies
6. UNIX for Dummies Questions & Answers
Hi all,
I am trying to winscp to RHEL5 server and i am ending up with following error.
Network error:connection timed out
The system is up and running but not able to winscp.
Tried SFTP,SCP and FTP protocols in winscp but none worked.
I can ssh into this server from another server... (3 Replies)
Discussion started by: lramsb4u
3 Replies
7. Solaris
Hi everyone,
I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies
8. Web Development
Lately my attention has been focused on distributed MySQL database replication to other web servers. All was going well, but then I noticed the replication would stop and there were there "Duplicate Primary Key" errors in SHOW SLAVE STATUS;
I started to trace these down and noticed that this... (2 Replies)
Discussion started by: Neo
2 Replies
9. UNIX for Advanced & Expert Users
I am trying to get my CVS client to connect to the repository over ssh. ssh works - I can quite happily log on but when I use the client - which incidentally is eclipse 2.1.3 on Windows using plink/puTTY as an external connection method - I get the following error in /var/log/secure:
error:... (2 Replies)
Discussion started by: Jdogg
2 Replies
10. UNIX for Dummies Questions & Answers
Hi,
I have created some users on my new enviroment on sun solaris in the aptempt to create a .profile which I did. I must have done something wrong because when I try to connect to one of this users it says:no shell, connection closed. The only thing I can think is that in my .profile I inserted... (2 Replies)
Discussion started by: giulianob
2 Replies
rshd(8c) rshd(8c)
Name
rshd - remote shell server
Syntax
/etc/rshd
Description
The command is the server for the routine and, consequently, for the program. The server provides remote execution facilities with authen-
tication based on privileged port numbers.
The is invoked by when it receives a connection on the port indicated in the cmd service specification. When a service request is
received, the following protocol is initiated:
1) The server checks the client's source port. If the port is not in the range 0-1023, the server aborts the connection.
2) The server reads characters from the socket up to a null (` ') byte. The resultant string is interpreted as an ASCII number, base
10.
3) If the number received in step 1 is non-zero, it is interpreted as the port number of a secondary stream to be used for the stderr.
A second connection is then created to the specified port on the client's machine. The source port of this second connection is
also in the range 0-1023.
4) The server checks the client's source address. If the address is associated with a host for which no corresponding entry exists in
the host name data base the server aborts the connection. For further information, see
5) A null terminated user name of at most 16 characters is retrieved on the initial socket. This user name is interpreted as a user
identity to use on the server's machine.
6) A null terminated user name of at most 16 characters is retrieved on the initial socket. This user name is interpreted as the user
identity on the client's machine.
7) A null terminated command passed to a shell is retrieved on the initial socket. The length of the command is limited by the upper
bound on the size of the system's argument list.
8) The command validates the user according to the following steps. The remote user name is looked up in the password file and a is
performed to the user's home directory. If either the lookup or fail, the connection is terminated. If the user is not the supe-
ruser, (user id 0), the file or is consulted for a list of hosts considered equivalent. If the client's host name is in this file,
the authentication is considered successful. If the lookup fails, or the user is the superuser, the file in the home directory of
the remote user, is checked for the machine name and identity of the user on the client's machine. If the lookup fails, the connec-
tion is terminated.
9) A null byte is returned on the connection associated with the stderr and the command line is passed to the normal login shell of the
user. The shell inherits the network connections established by
Diagnostics
All diagnostic messages are returned on the connection associated with the stderr, after which any network connections are closed. An
error is indicated by a leading byte with a value of 1 (0 is returned in step 9 above upon successful completion of all the steps prior to
the command execution).
locuser too long
The name of the user on the client's machine is longer than 16 characters.
remuser too long
The name of the user on the remote machine is longer than 16 characters.
command too long
The command line passed exceeds the size of the argument list (as configured into the system).
Hostname for your address unknown.
No entry in the host name database existed for the client's machine.
Login incorrect.
No password file entry for the user name existed.
No remote directory.
The command to the home directory failed.
Permission denied.
The authentication procedure described above failed.
Can't make pipe.
The pipe needed for the stderr was not created.
Try again.
A fork by the server failed.
/bin/sh: ...
The user's login shell could not be started.
Restrictions
The authentication procedure used here assumes the integrity of each client machine and the connecting medium. This is insecure, but is
useful in an open environment.
See Also
rsh(1c), rcmd(3x), services(5), inetd(8c)
rshd(8c)