Search squid archive

FWD: squid 3.2.0.16 access log no longer strictly increase...? *ouch* -- bug or feature?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



repost -- mailer bounded it -- for some reason it thinks that having multiple formats of a message to choose from is a security problem? Gee...
good think squid doesn't reject things with type-info, or it wouldn't work at all.

Guess things that reject all types are becoming the dinosaurs of the net.


To: squid-users@xxxxxxxxxxxxxxx
Subject: squid 3.2.0.16 access log no longer strictly increase...? *ouch* -- bug or feature?
Content-Type: multipart/alternative;
 boundary="------------090103050306030004050800"

This is a multi-part message in MIME format.
--------------090103050306030004050800
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


Got a surprise in a new version of squid 3.2.0.16 -- in monitoring my
log, my monitor prog burped and died.  It didn't like trying to
calculate the average rate over negative time period (for some reason it
doesn't realize that time
can run backwards and data is actually sucked back out...;-))

Is this normal now?  One of the things I changed recently was going from
syslog, which tends to be pretty good about not having times go backwards,
to 'diskd'....

Dunno if it is a bug or a feature, but it is a bit odd looking in a
time-progression based log.  I can at least prevent my script from gagging
at such, but is it supposed to be doing that??

Thanks -- sample times included below from log  -- ALL of these were
while I was connected to 'google', so ALL of them were 'CONNECT' log
messages, which might enter into the equation somewhere...
-linda
(** indicates time going backwards)

1332885640.662
1332885641.442
1332885641.431**
1332885641.436
1332885644.023
1332885663.344**
1332885663.515
...
1332885668.461
1332885670.637
1332885671.136
1332885672.015
1332885671.807**
1332885672.527
1332885672.325**
---------------------

p.s. -- OTOH, it could be a marketing feature... squid's so fast, it
fetches content in negative time!




--------------090103050306030004050800
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
  <style>
/* Linda's Style playground (c) 2011 L. A Walsh (permission given to
   do w/this anything other than claim my original as your own!
-- <a class="moz-txt-link-abbreviated" href="mailto:dept.playgrounds@xxxxxxxxx";>dept.playgrounds@xxxxxxxxx</a> )
*/
/* margin:(X):=T+B+R+L; (V H):V=T+B,H=R+L; (T H B):T,H=R+L, (T R B L) */

html, body {
font: 12pt "Lucida Console", monospace, fixed;
font-size-adjust:.50;
background-color:#f8fefb; color:#104060;
max-width:90ex;
}

table, tbody, tr, td {font: inherit;font-size 11.4pt; }

p { margin: 1em; text-indent:1em }
p+p { margin-top: .75em;margin-bottom:.75em }

small { font-size:85.18% }
big { font-size:117.4% }

quote { font-style:italic;
.l quote { font-style:italic; font-family:cursive,sans-serif;}

em { font-variant:small-caps }
h6 { font-size:85.180%/117.398% }
h5 { font-size:100%/132.824% }
h4 { font-size:117.398%/161.803% }
h3 { font-size:132.824%/200.00% }
h2 { font-size:161.803%/234.797% }
h1 { font-size:200.000%/265.648% }

h1, h2, h3, h4, h5 {font-size: inherit; font-weight:bold}

h5, h6 {font-size: inherit; font-variant:small-caps;}
hr {font-family:monospace:fixed; width:90ex; margin:0;left}
h5 {font: inherit; font-weight:800 }
h6 { font: inherit; font-weight:700 }
h1,h2,h3,h4,h5,h6 { margin:1em }

blockquote { margin:1em 1em; font-style:italic; }
blockquote &gt; p, blockquote &gt; blockquote {
 margin-top:0.50em;margin-bottom:0.50em; text-indent:0;}

pre, cite { margin: 1.2em .8em; }
pre, cite, tt {font-style:oblique; background-color:#f6f6f0; color:#202040;
font-family:"Lucida Console", monospace;
}
pre+pre {font-inherit; font-style:oblique;
background-color:#f6f6f0; color:#202040; margin:1ex .8em }

address {font inherit; font-style:oblique; font-family:"Cambria";}
address {font:inherit; margin:1em 3em; background-color:#f8faff;}
address+address {margin:0 2em}

img { margin:1.6em }

q {quotes:"“" "”" "‘" "’" }
q:before { content:open-quote }
q:after { content:close-quote }

a, a:link, a:focus, a:visited {text-decoration:underline}
a:link { color:#44BB33 }
a:focus { color: #22FF11 }
a:visited { color: #557722 }

.sig { font: oblique 15.75pt/84pt "Lucida Handwriting",cursive }
.sig:first-letter {
float:left;
font: italic 56pt/84pt "Lucida Calligraphy",cursive;
font-weight:200;
}

#sig_fl {
float:left;font:italic 56pt/84pt "Lucida Calligraphy",cursive;
font-weight:200;
}

@font-face {font-family:Verdana; panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face {font-family:Cambria; panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face {font-family:"Lucida Calligraphy"; panose-1:3 1 1 1 1 1 1 1 1 1;}
@font-face {font-family:"Lucida Handwriting"; panose-1:3 1 1 1 1 1 1 1 1 1;}

.MsoNormal, .MsoNormalTab {
padding:0; margin:0; color:"darkmagenta"; background:"honeydew";
font: oblique 100%/100% "Calibri","Verdana","Arial" !important;
}
span.MsoNormal , span.MsoNormalTable {
font-family: inherit !important; font-size: inherit !important; font-style:
inherit !important; color: inherit !important;
}
span[font-family=Arial], span[font-family="Times New Roman"],
font[face=Arial] ,font[face="Times New Roman"] {
font-family: inherit !important; font-size-adjust:inherit !important;
font-size: inherit !important; line-height: inherit !important;
color: inherit !important;
}
  </style>
<!-- vim: ts=1 sw=1 et sc fo=cqwa1 tw=78 syntax=css
-->
</head>
<body>
Got a surprise in a new version of squid 3.2.0.16 -- in monitoring my
log, my monitor prog burped and died.  It didn't like trying to
calculate the average rate over negative time period (for some reason
it doesn't realize that time<br>
can run backwards and data is actually sucked back out...;-))<br>
<br>
Is this normal now?  One of the things I changed recently was going
from <br>
syslog, which tends to be pretty good about not having times go
backwards, <br>
to 'diskd'....<br>
<br>
Dunno if it is a bug or a feature, but it is a bit odd looking in a
time-progression based log.  I can at least prevent my script from
gagging<br>
at such, but is it supposed to be doing that??<br>
<br>
Thanks -- sample times included below from log  -- ALL of these were<br>
while I was connected to 'google', so ALL of them were 'CONNECT' log<br>
messages, which might enter into the equation somewhere...<br>
-linda <br>
(** indicates time going backwards)<br>
<font face="Times New Roman, Times, serif"><br>
1332885640.662<br>
1332885641.442<br>
1332885641.431**<br>
1332885641.436<br>
1332885644.023<br>
1332885663.344**<br>
1332885663.515<br>
...<br>
1332885668.461<br>
1332885670.637<br>
1332885671.136<br>
1332885672.015<br>
1332885671.807**<br>
1332885672.527<br>
1332885672.325**<br>
---------------------<br>
<br>
</font><tt>p.s. -- OTOH, it could be a marketing feature... squid's so
fast, it fetches content in negative time!<br>
<br>
</tt><font face="Times New Roman, Times, serif"><br>
<br>
</font>
</body>
</html>

--------------090103050306030004050800--


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux