Sponsored Content
Operating Systems AIX Session never expired If i closed client prompt Post 302423046 by dearsumon on Thursday 20th of May 2010 04:55:43 AM
Old 05-20-2010
Thank you very much
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

mac 10.4>terminal>linux remote server>ssh login accepted>session closed-why?

mac 10.4>terminal>linux remote server>ssh login accepted>session closed-why? AHHHH!! I have been connecting to the server with the line: ssh userid@website.com The remote server accepts my password; logs me in with ssh; posts a lovely welcome message AND closes the session. Is this a "term... (0 Replies)
Discussion started by: xprankard
0 Replies

2. Solaris

Jumpstart on x86 client- prompt for CD2

Hi I just configured a jumpstart server for x86 and sparc clients. I don't use a dhcp server, so I configured /etc/ethers and did add_install_client to update /etc/bootparams. The sparc installation ist working, but the x86 installation stops after CD1 was successfully installed. What I did: I... (2 Replies)
Discussion started by: Jay_Fisi
2 Replies

3. Solaris

Expired password doesn't prompt for change

I'm on a Solaris 8 box that is not prompting users to change their password after it has expired. I have an older Solaris 8 box that does. We're accessing both via ssh. We have recently built the box that doesn't prompt from scratch. Obviously, we've overlooked something but we don't know what.... (2 Replies)
Discussion started by: mark24p
2 Replies

4. UNIX for Dummies Questions & Answers

Foreground shell script terminated when session expired

Hi, I ran a shell script in the foreground but it seems that the shell script teminated when the session expired. Please let me knw if it's possible or hypothesis is incorrect ASAP. (2 Replies)
Discussion started by: Ankgne
2 Replies

5. Solaris

expired password prompt at ssh login

Hi, I am using DSEE 6.3 to authenticate and authorize my Solaris 9 and 10 users. Everything works fine except password expiration. I use built-in global password policy for all users. The policy works well. However I could not find the right pam configuration in order to prompt users at ssh... (2 Replies)
Discussion started by: niyazi
2 Replies

6. Shell Programming and Scripting

Forcing a tty session but getting a password prompt?

I have a master host I want to use to issue some start/stop of LDAP services. I changed the client hosts /etc/sudoers to have Defaults:infra !requiretty The master host kicks off the jobs using the infra account doing a ssh session to the infra account on the clients. #!/bin/ksh ps -fu... (5 Replies)
Discussion started by: J-Man
5 Replies

7. Solaris

M5000 XSCF Console disconnecting when putty session is closed

Hi, I would appreciate some help. I remotely access, across a VPN, an M5000 and when I connect to the XSCF I can then access the OS using console -d0 and then I can get to the console. The problem I have is that I need to run something which will take many hours and I can't run it in the... (6 Replies)
Discussion started by: giles.cardew
6 Replies

8. AIX

Oracle Listener gets killed when root session is closed

Hi everyone, This is a strange thing, sometimes when I type > exit from root session, i get a message > There are processes running after this message is displayed the oracle listener dies out and have to startup the listener again. but this doesn't have always. Where should I start to... (5 Replies)
Discussion started by: filosophizer
5 Replies

9. AIX

Need to remote control client's ssh session

Is there a way that I can remotely control a user's ssh session so I can see what they are doing and walk them through the problem they are having on my AIX based application? (2 Replies)
Discussion started by: De@nneG
2 Replies

10. Red Hat

Getting "-bash-3.2#" prompt after logging to RHEL client

Hi, I am getting the -bash-3.2# prompt whenever I am trying to logging in the RHEL machine # ssh mindnic-02 root@mindnic-02's password: Last login: Thu May 25 14:06:31 2017 from 10.250.107.81 Could not chdir to home directory /root: No such file or directory -bash-3.2# Please help... (7 Replies)
Discussion started by: muzaffar.k
7 Replies
RLOGIND(8)						      System Manager's Manual							RLOGIND(8)

NAME
rlogind, in.rld - remote login server SYNOPSIS
login stream tcp nowait root /usr/sbin/in.rld in.rld tcpd login /usr/sbin/in.rld DESCRIPTION
Rlogind is the server for the rlogin(1) program. The server provides a remote login facility with authentication based on privileged port numbers from trusted hosts. Rlogind listens for service requests at the port indicated in the ``login'' service specification; see services(5). 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 checks the client's source address and requests the corresponding host name (see gethostbyaddr(3), hosts(5) and named(8)). If the hostname cannot be determined, the dot-notation representation of the host address is used. Once the source port and address have been checked, rlogind allocates a pseudo terminal (see tty(4)), and manipulates file descriptors so that the slave half of the pseudo terminal becomes the stdin , stdout , and stderr for a login process. The login process is an instance of the login(1) program, invoked with the -r option. The login process then proceeds with the authentication process as described in rshd(8), but if automatic authentication fails, it reprompts the user to login as one finds on a standard terminal line. The parent of the login process manipulates the master side of the pseduo terminal, operating as an intermediary between the login process and the client instance of the rlogin program. In normal operation, the packet protocol described in tty(4) is invoked to provide ^S/^Q type facilities and propagate interrupt signals to the remote programs. The login process propagates the client terminal's baud rate and terminal type, as found in the environment variable, ``TERM''; see environ(7). The screen or window size of the terminal is requested from the client, and window size changes from the client are propagated to the pseudo terminal. SEE ALSO
rlogin(1). 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. ``Try again.'' A fork by the server failed. ``/bin/sh: ...'' The user's login shell could not be started. BUGS
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. A facility to allow all data exchanges to be encrypted should be present. A more extensible protocol should be used. 4.2 Berkeley Distribution May 24, 1986 RLOGIND(8)
All times are GMT -4. The time now is 01:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy