05-02-2017
It looks like scrub cleared the counts and cleared the timestamp. Note that in the US Eastern timezone, the local time corresponding to the UNIX Epoch -- which is the time with timestamp 0 (midnight at the start of January 1, 1970 GMT) is Wed Dec 31 19:00:00 1969 EST.
9 More Discussions You Might Find Interesting
1. SCO
when I do a tape status /dev/rStp0 I get the following on a new tape and I have tried several:
Status : ready beginning-of-tape
soft errors : 0
hard errors: 2
underruns: 5
My BackupEdge has stopped backing up my system because it asks for a new volume yet my total system data is under 20... (5 Replies)
Discussion started by: psytropic
5 Replies
2. UNIX for Dummies Questions & Answers
Hello,
I am trying to show today's date and time in a better format than ‘date' (Using positional parameters). I found a command mktime and am wondering if this is the best command to use or will this also show me the time elapse since 1/30/70? Any help would be greatly appreciated, Thanks... (3 Replies)
Discussion started by: citizencro
3 Replies
3. Solaris
# zpool status -v
pool: pool1
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see:... (0 Replies)
Discussion started by: beginner
0 Replies
4. Hardware
Here is the error showing in the XCSF, can anyone recommend further diagnosis for this specific error?;
XSCF> showhardconf
SPARC Enterprise M3000;
+ Serial:PX61142029; Operator_Panel_Switch:Locked;
+ Power_Supply_System:Single; SCF-ID:XSCF#0;
+ System_Power:On;... (4 Replies)
Discussion started by: Touchpoint
4 Replies
5. Solaris
Hi,
I've gone around with this on Oracle's site (and tech support) and ended up empty handed and without ideas of what to do to fix the problem.
Background:
V245, Solaris 10, has 2 12-disk infortrend RAIDs attached.
Have replaced faulty disks many times - familiar with the routine. However,... (5 Replies)
Discussion started by: jdigjudy
5 Replies
6. Shell Programming and Scripting
I have a file that looks like:
file1:
www_blank_com 20121008153552
www_blank_com 20121008162542
www_blank_com 20121009040540
www_blank_com 20121009041542
www_blank_com 20121010113548
www_blank_com 20121011113551
www_blank_com 20121012113542
I want the new file to show the day of... (3 Replies)
Discussion started by: castrojc
3 Replies
7. UNIX for Dummies Questions & Answers
Hi all,
I've been working on a script to run a disk wipe (using Jim Garlick's scrub tool) on the filesystem in Xerox production printer RIPs.
Easy enough if there's just one partition, but I need to cater for the possibility of multiple drives/partitions, and either ZFS or UFS (don't know if... (2 Replies)
Discussion started by: DavidDawesFXA
2 Replies
8. Solaris
SOLARIS 9 Zone :
date command in crontab shows delayed(One Hour) output
Hi folks,
the date command shows the correct date and time, How ever, if the date command executed through crontab in any form of scrip the output shows as one hour delayed, similar to date -u..
Can some one help in... (12 Replies)
Discussion started by: judi
12 Replies
9. Shell Programming and Scripting
help me (1 Reply)
Discussion started by: sonu pandey
1 Replies
LEARN ABOUT CENTOS
mrtg-logfile
MRTG-LOGFILE(1) mrtg MRTG-LOGFILE(1)
NAME
mrtg-logfile - description of the mrtg-2 logfile format
SYNOPSIS
This document provides a description of the contents of the mrtg-2 logfile.
OVERVIEW
The logfile consists of two main sections.
The first Line
It stores the traffic counters from the most recent run of mrtg.
The rest of the File
Stores past traffic rate averates and maxima at increassing intervals.
The first number on each line is a unix time stamp. It represents the number of seconds since 1970.
DETAILS
The first Line
The first line has 3 numbers which are:
A (1st column)
A timestamp of when MRTG last ran for this interface. The timestamp is the number of non-skip seconds passed since the standard UNIX
"epoch" of midnight on 1st of January 1970 GMT.
B (2nd column)
The "incoming bytes counter" value.
C (3rd column)
The "outgoing bytes counter" value.
The rest of the File
The second and remaining lines of the file contains 5 numbers which are:
A (1st column)
The Unix timestamp for the point in time the data on this line is relevant. Note that the interval between timestamps increases as you
progress through the file. At first it is 5 minutes and at the end it is one day between two lines.
This timestamp may be converted in OpenOffice Calc or MS Excel by using the following formula
=(x+y)/86400+DATE(1970;1;1)
(instead of ";" it may be that you have to use "," this depends on the context and your locale settings)
you can also ask perl to help by typing
perl -e 'print scalar localtime(x),"
"'
x is the unix timestamp and y is the offset in seconds from UTC. (Perl knows y).
B (2nd column)
The average incoming transfer rate in bytes per second. This is valid for the time between the A value of the current line and the A
value of the previous line.
C (3rd column)
The average outgoing transfer rate in bytes per second since the previous measurement.
D (4th column)
The maximum incoming transfer rate in bytes per second for the current interval. This is calculated from all the updates which have
occured in the current interval. If the current interval is 1 hour, and updates have occured every 5 minutes, it will be the biggest 5
minute transfer rate seen during the hour.
E (5th column)
The maximum outgoing transfer rate in bytes per second for the current interval.
AUTHOR
Butch Kemper <kemper@bihs.net> and Tobias Oetiker <tobi@oetiker.ch>
2.17.4 2012-01-12 MRTG-LOGFILE(1)