Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Why there are /var/adm/messages.0,messages.1,messages.2,messages.3 Post 302626479 by Corona688 on Thursday 19th of April 2012 10:32:07 AM
Old 04-19-2012
It just means the logfiles were copied and reopened so they could be compressed and to prevent individual logs from getting too big. The exact details and timing depends on your log rotation system and can vary from system to system. They're likely configurable.

It would make sense for .0 to come before .1, look at them with ls -l to see which came first.

Last edited by Corona688; 04-19-2012 at 11:38 AM..
 

9 More Discussions You Might Find Interesting

1. Solaris

/var/adm/messages- Help

Solaris 8/ sun 420R Checked /var/adm/messages file and got the following message: Dec 4 16:40:05 serverXYZ ConfigProvider: get_pkg_instdate: getdate failed for the standard C locale (7) Does anyone know what this means? Looked up getdate but do not understand.... Thanks. (1 Reply)
Discussion started by: finster
1 Replies

2. UNIX for Advanced & Expert Users

error messages in /var/adm/messages

Hi, I have a SunFire V490, Solaris 10 with XP1024 storage and HP Library. I have noticed the following error messages in the /var/adm/messages file. These errors are being generated constantly. Also commands like devfsadm, format cfgadm etc are getting hung. After a reboot it works fine for a... (1 Reply)
Discussion started by: nitinp82
1 Replies

3. Solaris

Info req: /var/adm/messages - Kern.warning - different ID messages

Hi all, where I can find a list and meaning of the ID number (for example ID 353554 kern.warning)? Thanks in advance Pierluigi (1 Reply)
Discussion started by: Petrucci
1 Replies

4. Solaris

/var/adm/messages

Check message file and result posted below. Can anyone tell me what this is a sign of, what does it mean? server1% more messages.0 Dec 02 09:35:06 server1 bsd-gw: Inval id protocol request (65): AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA^\\2... (6 Replies)
Discussion started by: finster
6 Replies

5. Solaris

Help understanding [daemon.warning] messages in /var/adm/messages

Hi I've been using solaris for a few days now. During the install process i had some problems configuring my nic as i needed to install a third-party driver, which i got from a a linked site from the Sun Device Detector tool a ran prior to installing. I got it working eventually, but i'm... (1 Reply)
Discussion started by: jpg.2009
1 Replies

6. Solaris

[kern.warning] messages in /var/adm/messages

Hi Having looked through the log file /var/adm/messages i've noticed these kernel warning messages and i don't know what they mean: !-- @page { size: 8.5in 11in; margin: 0.79in } P { margin-bottom: 0.08in } --> cpudrv: NOTICE: cpu_acpi: _TSS package not found. cpudrv: WARNING:... (1 Reply)
Discussion started by: jpg.2009
1 Replies

7. Solaris

uamod messages in /var/adm/messages

Hello, I am using Solaris 10 and I'm geting the folowing error in /var/adm/messages. Feb 12 09:01:18 srp21ce1 uamod: NOTICE: (uamod480 @ Q 0x600159db710) set threshold to default values Feb 12 09:01:18 srp21ce1 uamod: NOTICE: (uamod480 @ Q 0x600159db710) threshold values... (4 Replies)
Discussion started by: toshibelul
4 Replies

8. 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

9. Solaris

Local zone is not logging systems messages to /var/adm/messages

This is isolated to just 1 non-global zone out of many zones managed This is a Solaris 11 system on SPARC This is NOT a branded zone syslogd is active This came to our attention when one of our scripts didn't run over the weekend prompting us to check our messages logging in... (6 Replies)
Discussion started by: samthewildone
6 Replies
Rotate(3pm)						User Contributed Perl Documentation					       Rotate(3pm)

NAME
Log::Agent::Rotate - parameters for logfile rotation SYNOPSIS
require Log::Agent::Rotate; my $policy = Log::Agent::Rotate->make( -backlog => 7, -unzipped => 2, -is_alone => 0, -max_size => 100_000, -max_time => "1w", -file_perm => 0666 ); DESCRIPTION
The "Log::Agent::Rotate" class holds the parameters describing the logfile rotation policy, and is meant to be supplied to instances of "Log::Agent::Driver::File" via arguments in the creation routine, such as "-rotate", or by using array references as values in the "-channels" hashref: See complementary information in Log::Agent::Driver::File. As rotation cycles are performed, the current logfile is renamed, and possibly compressed, until the maximum backlog is reached, at which time files are deleted. Assuming a backlog of 5 and that the latest 2 files are not compressed, the following files can be present on the filesystem: logfile # the current logfile logfile.0 # most recently renamed logfile logfile.1 logfile.2.gz logfile.3.gz logfile.4.gz # oldest logfile, unlinked next cycle The following switches are available to the creation routine make(), listed in alphabetical order, all taking a single integer value as argument: backlog The total amount of old logfiles to keep, besides the current logfile. Defaults to 7. file_perm The file permissions, given as an octal integer value, to supply to sysopen() during file creation. This value is modified during execution by the umask of the process. In most cases, it is good practice to leave this set to the default and let the user process controll the file permissions. Defaults to 0666. is_alone The argument is a boolean stating whether the program writing to the logfile will be the only one or not. This is a hint that drives some optimizations, but it is up to the program to guarantee that noone else will be able to write to or unlink the current logfile when set to true. Defaults to false. max_size The maximum logfile size. This is a threshold, which will cause a logfile rotation cycle to be performed, when crossed after a write to the file. If set to 0, this threshold is not checked. Defaults to 1 megabyte. max_time The maximum time in seconds between the moment we opened the file and the next rotation cycle occurs. This threshold is only checked after a write to the file. The value can also be given as a string, postfixed by one of the following letters to specify the period unit (e.g. "3w"): Letter Unit ------ ------- m minutes h hours d days d days w weeks M months (30 days of 24 hours) y years Defaults to 0, meaning it is not checked. max_write The maximum amount of data we can write to the logfile. Like "max_size", this is a threshold, which is only checked after a write to the logfile. This is not the total logfile size: if several programs write to the same logfile and "max_size" is not used, then the logfiles may never be rotated at all if none of the programs write at least "max_write" bytes to the logfile before exiting. Defaults to 0, meaning it is not checked. single_host The argument is a boolean stating whether the access to the logfiles will be made from one single host or not. This is a hint that drives some optimizations, but it is up to the program to guarantee that it is accurately set. Defaults to false, which is always a safe value. unzipped The amount of old logfiles, amongst the most recent ones, that should not be compressed but be kept as plain files. Defaults to 1. To test whether two configurations are strictly identical, use is_same(), as in: print "identical " if $x->is_same($y); where both $x and $y are "Log::Agent::Rotate" objects. All the aforementioned switches also have a corresponding querying routine that can be issued on instances of the class to get their value. It is not possible to modify those attributes. For instance: my $x = Log::Agent::Rotate->make(...); my $mwrite = $x->max_write(); would get the configured max_write threshold. AUTHORS
Originally written by Raphael Manfredi <Raphael_Manfredi@pobox.com>, currently maintained by Mark Rogaski <mrogaski@cpan.org>. Thanks to Chris Meshkin for his suggestions on file permissions. SEE ALSO
Log::Agent(3), Log::Agent::Driver::File(3), Log::Agent::Rotate::File(3). perl v5.10.0 2002-05-14 Rotate(3pm)
All times are GMT -4. The time now is 06:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy