01-28-2010
The log already says it. It simply says there have been 3 failed attempts from your box with a wrong password (3 tries in 1 second, maybe a script?) and 16 seconds later it worked.
9 More Discussions You Might Find Interesting
1. Solaris
Hi,
What are the critical logs need constant monitoring ?
thanks (2 Replies)
Discussion started by: sol8admin
2 Replies
2. UNIX for Dummies Questions & Answers
what is a critical section?why multipleprocesses or multiplethreads cant be given a chance to access the critical section?
please explain me with an example.
thanks (3 Replies)
Discussion started by: compbug
3 Replies
3. Shell Programming and Scripting
We have a batch job which runs and checks for certain files on a server and retrieves them to our server.
But from last few hours the job is not running correctly.
It gives msg file now found when there are files present on the server..
Nothing has been changed.................. (1 Reply)
Discussion started by: shikhakaul
1 Replies
4. HP-UX
Dear(s),
anybody have played ServiceGuard on HP-UX version 11.23 MC ?
I am planning to install Oracle and OpenView Operations for Unix 8 on a ServiceGuard clustered HP-UX environment, any suggestionsfrom where should I start ?
Best Regards,
Mostafa Reda (1 Reply)
Discussion started by: darousha
1 Replies
5. UNIX for Advanced & Expert Users
Hi,
I am trying to create a shared library from a .c file using
gcc -c -fpic -I/usr/local/include Chksum.C -o Chksum.o
gcc -shared -o libtclcksum.so Chksum.o
when i try to load this shared library libtclcksum.so in tclsh
% load libtclcksum.so
I get the following error:
couldn't load... (1 Reply)
Discussion started by: archana485
1 Replies
6. HP-UX
The following files were wiped out - new empty files were left in their place.
/etc/inittab, /etc/inetd.conf, and /etc/MANPATH
The system is running HP-UX 11i v3 - Mar08.
Anyone seen anything like this?
Any ideas on a way to figure this out if it happens again or a suggested way to... (9 Replies)
Discussion started by: KEnglander
9 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am using Ubuntu 10.04. Recently I have seen this error appear in my terminal as I edit text files with gedit:
(gedit:2841): Gtk-CRITICAL **: gtk_widget_is_ancestor: assertion `ancestor != NULL' failed
Any ideas on what this means?
Mike (1 Reply)
Discussion started by: msb65
1 Replies
8. UNIX for Advanced & Expert Users
Hello
I have moved a critical lib from its location, so all programms linked to libc dont work .
I still have two shells on the machine, bash and ksh
The only thing I see is copying back the lib, but of course : dd, cp , mv etc are dead .
So i tryed a loop with read ...
{^Jwhile read... (24 Replies)
Discussion started by: remi75
24 Replies
9. Solaris
Hi all,
Few hours ago I did some changes in our Solaris cluster servers. Below are changes I did :
1. Installed latest Solaris 10 patchset from oracle.
2. Enabled BSM log module. Entered into single user mode and rebooted. After reboot changed to multi-user mode and rebooted again.
Now... (7 Replies)
Discussion started by: sembii
7 Replies
LEARN ABOUT OPENDARWIN
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)