Sponsored Content
Full Discussion: Time out Issue
Homework and Emergencies Emergency UNIX and Linux Support Time out Issue Post 302957182 by Scrutinizer on Thursday 8th of October 2015 03:34:03 AM
Old 10-08-2015
This could also be caused by timeout settings of a network component, for example a firewall between the user and the server. What happens when you connect from a host in the same network segment?

Is it a OS level login or an application login? If the latter, then the timeout may be caused by the application.
 

8 More Discussions You Might Find Interesting

1. Solaris

Time issue on ultra 10

I am running solaris 8 on an ultra 10... Every so often it has an issue with the time... The time seems to stop - ie. when I issue the date command the time is not changing... therefore anything in cron doesnt run. When I set the date again - its fine for a few weeks and then it pauses again.... (3 Replies)
Discussion started by: frustrated1
3 Replies

2. HP-UX

Time Modified Issue Please Assist

I am trying to periodically check that the environment variables have not been changed on a HP-UX server. This was going to be easy except I ran into the odd circumstance of having two files that should be created equally be created differently when one is created by command line and the other is... (1 Reply)
Discussion started by: Emancipator
1 Replies

3. Shell Programming and Scripting

Convert Epoch Time to Standard Date and Time & Vice Versa

Hi guys, I know that this topic has been discuss numerous times, and I have search the net and this forum for it. However, non able to address the problem I faced so far. I am on Solaris Platform and unable to install additional packages like the GNU date and gawk to make use of their... (5 Replies)
Discussion started by: DrivesMeCrazy
5 Replies

4. Shell Programming and Scripting

Perl, time stamp issue. 60th minutes

Hi Guys, Could you tell me how you can get the time stamp for 60th minutes? Currently, we name our file using time stamp upto minutes and then add seconds at the end starting from 01. And when the seconds reaches 60 we simply add 1 to the time stamp and reset the seconds to 00. But the... (3 Replies)
Discussion started by: supaLucas
3 Replies

5. Red Hat

Time Sync issue on RHEL 5.3

Hi, My Linux VMs are running on citrix XEN.Somehow the time drift is too high (going very fast). Even if the correct time configured using date -s command, for every 1 hr it is differing almost 5 - 10 mins. Tried configuring ntpd (local NTP server) and still it is not synchronized. Machine... (2 Replies)
Discussion started by: uday123
2 Replies

6. Linux

cifs.upcall issue, requests new kerberos service ticket all the time

This is more of an annoyance than an actual production issue. I've set it up so that each user's home directory is mounted to an immediate subdirectory of $HOME when they login, (and umounts when they log out to keep /proc/mounts a manageable size). My issue comes in when my login scripts... (0 Replies)
Discussion started by: thmnetwork
0 Replies

7. Red Hat

File access time issue

Hi, I am facing a weird file access time issue on redHat5.x. I have a program which will scan the files in the NFS system and delete files which are older than 4 days, before deleting files program will print the access time of the file. Some of the files are getting deleted which are not older... (1 Reply)
Discussion started by: Satyak
1 Replies

8. UNIX for Advanced & Expert Users

NTP time issue with md5 authentication.

Hi All Appreciate your help. Here is the scenario: 1. Five months back we configured md5 authentication with network devices and NTP server and it worked fine. 2.Last week all of a sudden the network devices are out of sync. 3.We changed the md5 key and it started working. ... (0 Replies)
Discussion started by: iqtan
0 Replies
rlogind(8c)															       rlogind(8c)

Name
       rlogind - remote login server

Syntax
       /etc/rlogind

Description
       The server is used for the program.  The server provides a remote login facility with authentication based on privileged port numbers.

       The  server is invoked by when it receives a connection on the port indicated in the login service specification.  For further information,
       see 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.  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, allocates a pseudo terminal and manipulates file descriptors so that the slave half of
       the pseudo terminal becomes the stdin, stdout, and stderr for a login process.  For further information, see

       The login process is an instance of the program, invoked with the option.  The login process then proceeds with the authentication  process
       as described in but if automatic authentication fails, it reprompts the user to log in on a standard terminal line.

       The  parent of the login process manipulates the master side of the pseudo terminal, operating as an intermediary between the login process
       and the client instance of the program.	In normal operation, the packet protocol described in 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.  For further information see

       The screen or window size of the terminal is requested from the client, and any changes in the window size from the client are sent to  the
       pseudo terminal.

Restrictions
       The authentication procedure used here assumes the integrity of each client machine and the connecting medium.  This is insecure, but it is
       useful in an open environment.

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.

       Hostname for your address unknown
       No entry in the host name database existed for the client's machine.

       Try again
       A fork by the server failed.

       /bin/sh: ...
       The user's login shell could not be started.

See Also
       rlogin(1c), inetd(8c)

																       rlogind(8c)
All times are GMT -4. The time now is 06:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy