Hi all,
I´m replacing an old linux enterprise redhat 4.5 by a new one linux enterprise redhat 6.
In both I use rexec as a communication between the front end and the user.
In the old one, when the user connects, the communication establishes quickly (less than 3 sec). But in the new one, the communication establishes very slow (30 sec. aprox.).
I have reviewed the configurations and the only difference is:
in the old one, the parameter of log_on_success += USERID and log_on_failure += USERID does not exists.
But if I disable those parameters in /etc/xinet.d/rexec in the new one, I can not log.
Anybody have faced a similar problem?
Thanks in advance
When I ssh to my box, an Ultra 5. I get prompted for password immediately. I enter it and have to wait sometimes a full minute for it to prompt for a password.
The same thing happens when i try to ftp to the box, it will say connected, but it takes forever to prompt for password, and... (2 Replies)
Running open solaris on a e420 that I recently picked up. Having issues sshing to it from either of my Linux boxes as its very slow to login (from the solaris box to the linux box it connects just fine.
Here is the output of ssh -vvv. I have hightlighted where it seems the slowdown is. Does... (0 Replies)
Hi,
Quick question, I'm messing about with a test box at work (system v)
Basically I telnet to the server.
Get the following :
SunOS 5.9
login: (my name)
Password: (my password)
Last login: Thu Feb..... yada yada
(At this stage it takes over a minute to come to display the... (5 Replies)
Hi All,
I have problem when i write my user name to login to my server late (about 10 min) to give me field of password
if u know how i can solve it?
Thanks (4 Replies)
Hi Guys and Girls, I know this is a common question but I've searched and we've tried the suggestions without luck. When I log into the box via SSH from a windows machine I get a 1 min 20 sec delay. If we add my IP address and machine name to /etc/hosts then I get an instant login. I would be happy... (12 Replies)
I have some sample code that's supposed to ssh to another machine using Net::SSH::Perl, execute a command, and print
the output of that command. It's very basic, and it works. However, I noticed that upon logging in:
$ssh->login('username','password');
It takes roughly 10-13 seconds to... (2 Replies)
Hi, I have the following issue, when I tried to login to an Openindiana remote server through ssh It takes to long to ask me for the password. So i tried -v and I realize that sshd hangs here " debug1: SSH2_MSG_SERVICE_ACCEPT received " for at least 2 minutes. Then I can log in and everything is... (2 Replies)
Version: Oracle Enterprise Linux 6.3
Running on VMWare Workstation
When I login to my Linux VM from putty, the third line prompting for password comes only after few seconds.
login as: root
Access denied
root@192.168.0.235's password: ---> It takes around 5 seconds to get this prompt
I... (1 Reply)
Hello I have a LPAR AIX 6.1 on Power VM, Vio 2.2.3 and when I execute a rcp to this machine, I cant, simultaneosly, rlogin, telnet, rsh to this same LPARt. This commands stay hanged till the copy end, and Imeddiatlely the comand is executed (rlogin, telnet, rhs, etc).
Someone can give me... (1 Reply)
Discussion started by: artur_dietrich
1 Replies
LEARN ABOUT MINIX
xinetd.log
XINETD.LOG(5) File Formats Manual XINETD.LOG(5)NAME
xinetd.log - xinetd service log format
DESCRIPTION
A service configuration may specify various degrees of logging when attempts are made to access the service. When logging for a service is
enabled, xinetd will generate one-line log entries which have the following format (all entries have a timestamp as a prefix):
entry: service-id data
The data depends on the entry. Possible entry types include:
START generated when a server is started
EXIT generated when a server exits
FAIL generated when it is not possible to start a server
USERID generated if the USERID log option is used.
NOID generated if the USERID log option is used, and the IDONLY service flag is used, and the remote end does not identify
who is trying to access the service.
In the following, the information enclosed in brackets appears if the appropriate log option is used.
A START entry has the format:
START: service-id [pid=%d] [from=%d.%d.%d.%d]
An EXIT entry has the format:
EXIT: service-id [type=%d] [pid=%d] [duration=%d(sec)]
type can be either status or signal. The number is either the exit status or the signal that caused process termination.
A FAIL entry has the format:
FAIL: service-id reason [from=%d.%d.%d.%d]
Possible reasons are:
fork a certain number of consecutive fork attempts failed (this number is a configurable parameter)
time the time check failed
address the address check failed
service_limit the allowed number of server instances for this service would be exceeded
process_limit a limit on the number of forked processes was specified and it would be exceeded
A DATA entry has the format:
DATA: service-id data
The data logged depends on the service.
login remote_user=%s local_user=%s tty=%s
exec remote_user=%s verify=status command=%s
Possible status values:
ok the password was correct
failed the password was incorrect
baduser no such user
shell remote_user=%s local_user=%s command=%s
finger received string or EMPTY-LINE
A USERID entry has the format:
USERID: service-id text
The text is the response of the identification daemon at the remote end excluding the port numbers (which are included in the response).
A NOID entry has the format:
NOID: service-id IP-address reason
SEE ALSO xinetd(1L), xinetd.conf(5)
28 April 1993 XINETD.LOG(5)