On Sat, 29 May 2004, Evgeny Kotsuba wrote:
> KEY 00809CE0307E5229705C06DD4D186146
> STORE_OK NOT_IN_MEMORY SWAPOUT_DONE PING_NONE
> CACHABLE,VALIDATED
Yes..
> if (mem)
> storeAppendPrintf(s, "\t%s %s\n",
> RequestMethodStr[mem->method], mem->log_url);
These lines is not active in the fragment above.. the object information
above is for an object without a memory object.
The spaces you ask about is from describeStatuses() aligns the fields. The
reason why you see a single space between the other fields is because in
this specific object the field values for the other fields is at their
maximum length.
KEY md5key(16)
storeStatus(13) memStatus(13) swapStatus(12) pingStatus(12)
storeEntryFlags(comma separated)
timestamps
lock, client & reference counters
swap file location
mem object info (URL, method etc, only if there is a mem object)
Regards
Henrik
Received on Sun May 30 2004 - 12:33:24 MDT
This archive was generated by hypermail pre-2.1.9 : Mon May 31 2004 - 12:00:02 MDT