Sponsored Content
Full Discussion: (/var/log/messages) issue
Top Forums UNIX for Dummies Questions & Answers (/var/log/messages) issue Post 302373508 by mojoman on Friday 20th of November 2009 01:29:46 PM
Old 11-20-2009
How do I turn on system accounting?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/var/log/messages

Which programm, deamon or script is responsible for filling the file /var/log/messages ? (1 Reply)
Discussion started by: Cozmic
1 Replies

2. Solaris

diff b/w /var/log/syslog and /var/adm/messages

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)
Discussion started by: tv.praveenkumar
2 Replies

3. UNIX for Advanced & Expert Users

/var/adm/messages vs /var/log/messages

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)
Discussion started by: gomes1333
2 Replies

4. Solaris

Difference between /var/log/syslog and /var/adm/messages

Hi, Is the contents in /var/log/syslog and /var/adm/messages are same?? Regards (3 Replies)
Discussion started by: vks47
3 Replies

5. Shell Programming and Scripting

How can view log messages between two time frame from /var/log/message or any type of log files

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)
Discussion started by: johnveslin
1 Replies

6. UNIX for Dummies Questions & Answers

fprintd messages in /var/log/messages

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)
Discussion started by: JakesHat
3 Replies

7. SuSE

Some error messages in var/log/messages

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)
Discussion started by: JDBA
2 Replies

8. Shell Programming and Scripting

Log all the commands input by user at real time in /var/log/messages

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)
Discussion started by: invinzin21
12 Replies

9. Shell Programming and Scripting

Transfer the logs being thrown into /var/log/messages into another file example /var/log/volumelog

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

10. Red Hat

Meaning of /var/log/messages

I am getting a lot of message as follows in /var/log/message files as follows. messages.1:559:May 4 20:01:56 SERVER2 kernel: session_stat: sync=0 async=33 aretr=0 messages.1:560:May 4 20:02:42 SERVER2 kernel: session_stat: dev=fd:5 state=6 blksize=4096 mmapsize=262144 messages.1:561:May 4... (2 Replies)
Discussion started by: Anjan Ganguly
2 Replies
CCZE(1) 							       CCZE								   CCZE(1)

NAME
ccze - A robust log colorizer SYNOPSIS
ccze [options] <logfile DESCRIPTION
This manual page documents briefly the ccze utility, which is a drop-in replacement for colorize, but written in C, to be faster and less resource-hungry. The goal was to be fully backwards compatible, yet superior with respect to speed and features. OPTIONS
These programs follow the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is included below. -a, --argument PLUGIN=ARGUMENTS Use this option to pass ARGUMENTS to the specified PLUGIN. The argument list is whitespace separated. -A, --raw-ansi If one wants to enable raw ANSI color sequences instead of using curses, this option does just that. -c, --color KEY=COLOR Set the color of the keyword KEY to COLOR, like one would do in one of the configuration files. -C, --convert-date Convert unix timestamp to readable date format (in oops and squid logs, for example). -F, --rcfile rcfile Read rcfile as a configuration file upon startup, instead of the default ones. -h, --html Instead of colorising the input onto the console, output it in HTML format instead. -l, --list-plugins List all available (loaded) plugins, along with their type and a short description. -m, --mode mode Change the output mode. Available modes are curses, ansi and html. -o, --options OPTIONS... CCZE is able to toggle some of its features with this option. You can toggle the scroll, wordcolor, lookups, and transparent fea- tures, or you can fiddle with cssfile. All of these are enabled by default, except cssfile. One can turn them off by prefixing the option with a "no". With scroll, one can enable or disable scrolling. If the output is not redirected, it is wise to leave it enabled. The wordcolor option makes ccze search for different keywords in unparsed input, and color those too. Since it is quite fast, and makes the output look better, it is recommended to leave this enabled. However, lookups is an option that might be better to disable. When on, ccze will try to look up usernames, service names, and lots of other stuff, which will slow down coloring a great deal. If one is piping a long log through ccze, this option might be turned off to speed up the process. With the transparent option, one can make CCZE treat black background colors as transparent - that means, a black background will appear transparent in a similar X terminal. If turned off, it will appear as black. If cssfile is set, then CCZE will not inline the Cascading Style Sheet information into the outputted HTML, but include a link to the external stylesheet given in this parameter. -p, --plugin PLUGIN While the default action is to load all plugins (see the Plugins section below), when this option is present, only the specified plugins will be loaded. If one knows what kind of log will be piped through ccze, using this option may result in a slight speedup. -r, --remove-facility Syslog-ng puts the facility level before log messages. With this switch, these can be cut off. --help Show summary of options and exit. -V, --version Show version of program. PLUGINS
Different programs have different kind of logs, and every kind of log ccze supports is implemented via a plug-in. They are by default located under /usr/lib/ccze and $HOME/.ccze (so they can be overridden by the user easily). At the moment, the following modules are bundled with the official release: apm For coloring apmd's logs. distcc For coloring distccd's logs. (See distccd(1)) exim For coloring exim's main.log. (See exim(8)) fetchmail For coloring fetchmail's log files. (See fetchmail(1)) ftpstats For coloring ftpStats compatible log files, such as Pure-FTPD's Stats log format. httpd For coloring apache-style access.log and error.log files. (See apache(8)) As a side-effect, all compatible formats, like pure-ftpd(8)'s common-log format is also supported by this plugin. icecast For coloring icecast/icecast.log and icecast/usage.log files. (See icecast(8)) oops For coloring oops/oops.log files. php For coloring php.log files. postfix For coloring postfix logs. (See postfix(1)) procmail For coloring procmail's log file. (See procmail(1)) proftpd For coloring proftpd's access.log and auth.log files. (See proftpd(8)) squid For coloring squid's access.log, store.log and cache.log files. (See squid(8)) sulog For coloring sulog files. (See su(1)) super For coloring super.log files. (See super(1)) syslog For coloring generic syslog messages. (See syslogd(8)) ulogd For coloring ulogd logs. vsftpd For coloring vsftpd.log files. (See vsftpd(8)) xferlog For coloring xferlog files. (See xferlog(5)) FILES
/etc/colorizerc, $HOME/.colorizerc These files are the default configuration files for colorize, and are parsed by ccze for the sake of full compatibility. /etc/cczerc, $HOME/.cczerc This two are the main configuration files, in which one can change the colors used by the program to his liking. See the comments in the beginning of /etc/cczerc for a description on the files' structure. If neither of these files exist on your system, consider using the ccze-dump utility in the source tree, which dumps the default color set to standard output. SEE ALSO
colorize(1) AUTHOR
ccze was written by Gergely Nagy <algernon@bonehunter.rulez.org>, based on colorize by Istvan Karaszi <colorize@spam.raszi.hu>. CCZE 0.2.1 2003-04-24 CCZE(1)
All times are GMT -4. The time now is 09:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy