Nov 26 09:57:05 BigNAS kernel: xor: automatically using best checksumming function: pIII_sse

Nov 26 09:57:05 BigNAS kernel: pIII_sse : 10092.000 MB/sec

Nov 26 09:57:05 BigNAS kernel: xor: using function: pIII_sse (10092.000 MB/sec)

 

This is the only minor issue in my Syslog. Server is working fine but any ideas on this? Would be nice to be issue free

 

On a Asus P5Q Pro, 2GB Corsair, E5300

thats not an error...informational message.

Yeah. Realised it was a minor issue so just changed my initial post. Still, would be nice to not have it but ah well

Its a unMenu undocumented feature...

Its a unMenu undocumented feature...

Here's another undocumented feature... you can easily change the way that the syslog lines are colored.

 

You can edit your  syslog_match.conf file using the Config View/Edit page in unmenu.

 

In the file, add a line near the top like this:

match_case||"using best checksumming"||black

It should be near the other few lines with black on the end of the line

 

Thar new pattern you added will match before any of the patterns that make a line show in color. 

It will then use "black" when matching the line you are complaining about

(matching the words using best checksumming)  Once a line has been matched in the file, no other lines further down in the file will be matched.

 

The line being matched was looking for the string of characters checksum preceded by a space. 

 

It matched the partial string of character in the word "checksumming"

As an alternate solution, you can delete the line in the file that looks like this:

match_case||" checksum"||orange

 

The initial part of the line "match_case" specifies that the exect case of the string be matched.  If it was "any_case" then capitalization would not matter, it would match either lower or upper or mixed case.

 

Now that you know how it works, you can edit the syslog_match.conf  file as you desire, and highlight (or not) anything you desire that might be specific to your hardware.

 

All patterns matched/colored in the syslog display in unMENU are informational.... they are those RobJ initially decided to highlight in red, orange, blue, etc (he wrote the initial colorizing code)

 

The specific lines being highlighted were initially defined many versions of unRAID ago... and the messages sent to the log under Linux have changed over the past few years, so lines may not be the original ones RobJ was targeting.    It is likely he was targeting a line describing a checksum error of some kind, not how it will be doing the xor calculations. 

 

Now... RobJ is about the best at looking at and understanding syslog files.  Those lines interesting to him are usually those he looks for when helping users with their systems.  At some point, with any luck, he'll assist in updating the file for current syslog content.

 

Joe L.

 

Thanks for an excellent response. Kind of made me smile for some reason.

Here's another undocumented feature... you can easily change the way that the syslog lines are colored.

 

I have to say I love unMenu even [glow=green,2,300]more[/glow] now.