It is crazy when you just entered a command example sudo or su or even ps. It will flood your /var/log/messages. Please see duplicate entries except for the pid. At 1 specific time.
Thanks
Code:
[user1@SERVER1:~]$ cat b
Jan 13 17:09:05 SERVER1 bash[727]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[731]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[735]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[739]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[745]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[749]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[753]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[757]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[761]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[765]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[769]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[773]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[783]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[787]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[791]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[795]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[801]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[805]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[809]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[813]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[823]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[827]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[831]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[835]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[841]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[845]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[849]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[854]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[858]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[862]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[866]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[870]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[874]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[884]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[888]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[892]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[896]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[900]: user1 as root:
Jan 13 17:09:05 SERVER1 bash[904]: user1 as root:
[user1@SERVER1:~]$
Moderator's Comments:
Please use CODE tags as required by forum rules!
Last edited by RudiC; 01-13-2017 at 04:48 PM..
Reason: Added CODE tags.
hi sirs
can u tell the difference between /var/log/syslogs and /var/adm/messages
in my working place i am having two servers.
in one servers messages file is empty and syslog file is going on increasing..
and in another servers message file is going on increasing but syslog file is... (2 Replies)
The /var/adm/messages in Solaris seem to log more system messages/errors compared to /var/log/messages in Linux.
I checked the log level in Linux and they seem OK.
Is there any other log file that contains the messages or is it just that Linux doesn't log great many things? (2 Replies)
How can view log messages between two time frame from /var/log/message or any type of log files.
when logfiles are very big and especially many messages with in few minutes, I would like to display log messages between 5 minute interval.
Could you pls give me the command? (1 Reply)
Whenever a user uses su I get the following error messages in /var/log/messages:
Nov 23 04:24:55 <REMOVED> abrt: saved core dump of pid 26141 (/usr/libexec/fprintd) to /var/spool/abrt/ccpp-1322018695-26141.new/coredump (753664 bytes)
Nov 23 04:24:55 <REMOVED> abrtd: Directory... (3 Replies)
Hi all
I have a newly installed Oracle X2-4 server running Solaris 10 x86 with the latest patches.
I have one non-global zone configured running an Oracle DB instance.
After configuring IPMP failover between two NICs on the server and rebooting I am seeing the /var/adm/messages being flooded... (7 Replies)
How are you?
SUSE V10 and 11.
In /var/log/messages I see these lines in some servers. I'd like to know what causes these errors and how to fix them.
Thank you,
error: PAM: Authentication failure for root from XXXXXXXX
Did not receive identification string from XXXXXXX
Invalid user suse-gm... (2 Replies)
Below is my script to log all the command input by any user to /var/log/messages. But I cant achieve the desired output that i want. PLease see below.
function log2syslog
{
declare COMMAND
COMMAND=$(fc -ln -0)
logger -p local1.notice -t bash -i -- "$USER:$COMMAND"
}
trap... (12 Replies)
I have been searching and reading about syslog. I would like to know how to Transfer the logs being thrown into /var/log/messages into another file example /var/log/volumelog.
tail -f /var/log/messages
dblogger: msg_to_dbrow: no logtype using missing
dblogger: msg_to_dbrow_str: val ==... (2 Replies)
Discussion started by: kenshinhimura
2 Replies
LEARN ABOUT DEBIAN
calife.auth
CALIFE.AUTH(5) BSD File Formats Manual CALIFE.AUTH(5)NAME
calife.auth -- format of the calife authorization file
DESCRIPTION
The calife.auth files are files consisting of newline separated records, one per user, containing three colon (``:'') separated fields.
These fields are as follows:
name User's login name / @group.
shell User's shell
user1,user2,...,usern
List of logins allowed for the user name
The name field is the login used to access the computer account.
The login name must never begin with a hyphen (``-''); also, it is strongly suggested that neither upper-case characters or dots (``.'') be
part of the name, as this tends to confuse mailers. No field may contain a colon (``:'') as this has been used historically to separate the
fields in the user database.
One alternative syntax is to use @group to specify that any user in the given group is allowed to use calife to become root.
The shell field is the command interpreter the user prefers. If there is nothing in the shell field, the user's current shell as found in
the (/etc/passwd) file is assumed.
If the shell field is '*', then the account is considered as locked and access is denied.
If the third parameter is specified, it is assumed to be the list of login the current user has the right to become. It enables use of calife
for non-root only accounts.
calife.auth is placed in /etc.
EXAMPLE
# calife.auth-dist
#
# Format
#
# name[:shell_to_be_run][:user1,user2,usern]
#
fcb
roberto:/bin/tcsh
pb::guest,blaireau
SEE ALSO calife(1), su(1)HISTORY
A calife.auth file format appeared in DG/UX and SunOS, written for Antenne 2 in 1991. It has evolved with the extra shell specification. The
login list was reintroduced in 2.7.
AUTHOR
Ollivier Robert <roberto@keltia.frmug.fr.net>
BSD September 25, 1994 BSD
01-13-2017
