I'm getting this on my Solaris VM, running current trunk:
Mar 8 19:44:41 solaris11 traffic_server[26419]: [ID 702911
daemon.error] {1} ERROR: bad hardware sector size
Does anyone else (using Solaris) see this too? This is using a cache on
the file system.
-- leif
- Original Message -
> I made a few tweaks to the documentation generator.
>
> * A navigation bar is now available. This is auto generated if there
> id a file named "order.txt" in the directory that contains the
> pages. This file is simply a white space separated list of the stems
> for
Inspired by reading Rich Bowen's presentation:
http://www.slideshare.net/rbowen/write-a-better-fm
which everybody should read!
- Original Message -
> Due to the "it's never enough" effect I have extend the use specified
> nav bar links syntax. If you add a link that has a name of "Top",
>
I have some questions with the design of class Part. I think the Part is
divided into several Segments, and each Segments contain 2^16 buckets, and
each buckets contain 4 object. In default, every object's size is
8000(proxy.config.cache.min_average_object_size), and each object has an
opposite
