Mailing List Archive: Cherokee: dev

Issue 511 in cherokee: trace output timestamps

Index | Next | Previous | View Threaded

codesite-noreply at google

Jun 25, 2009, 12:49 PM

Post #1 of 5 (219 views)
Permalink

Issue 511 in cherokee: trace output timestamps

Status: New
Owner: ----

New issue 511 by binb...@b2host.de: trace output timestamps
http://code.google.com/p/cherokee/issues/detail?id=511

What steps will reproduce the problem?
1. enable trace output in cherokee

What is the expected output? What do you see instead?
Expected output would be timestamps with microseconds.
The current format doesn't support them.
It makes no sense to see a timestamp in front of each line which doesn't
change especially in the case when processing lasts less than a second.

What version of the product are you using? On what operating system?
cherokee 0.99.19
CentOS 5.3 x86_x64

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Jun 25, 2009, 1:24 PM

Post #2 of 5 (205 views)
Permalink

Issue 511 in cherokee: trace output timestamps [In reply to]

Updates:
Owner: ste...@konink.de
Labels: Type-Enhancement Priority-Low OpSys-All Component-Logic Usability

Comment #1 on issue 511 by ste...@konink.de: trace output timestamps
http://code.google.com/p/cherokee/issues/detail?id=511

Here you go.

Attachments:
binB4SH.diff 1.4 KB

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Jun 25, 2009, 2:24 PM

Post #3 of 5 (202 views)
Permalink

Issue 511 in cherokee: trace output timestamps [In reply to]

Comment #2 on issue 511 by binb...@b2host.de: trace output timestamps
http://code.google.com/p/cherokee/issues/detail?id=511

I changed format of the timestamp on my system to be more like

cherokee_buffer_add_va (&entries, "[%02d/%02d/%d %02d:%02d:%02d %03d] ",
now.tm_mday,
now.tm_mon,
now.tm_year + 1900,
now.tm_hour,
now.tm_min,
now.tm_sec,
now_time.millitm);

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Jun 26, 2009, 6:23 AM

Post #4 of 5 (201 views)
Permalink

Issue 511 in cherokee: trace output timestamps [In reply to]

Updates:
Status: Fixed
Owner: alobbs

Comment #3 on issue 511 by alobbs: trace output timestamps
http://code.google.com/p/cherokee/issues/detail?id=511

r3390 has implemented it:
http://svn.cherokee-project.com/changeset/3390

Besides adding milliseconds support, it also gets rid of a system call.
(Actually, it will call the syscall anyway.
However, in this case, the new time value might be useful for the rest of
the server).

Thanks guys for the RFE and the patch proposal!!

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

codesite-noreply at google

Jun 26, 2009, 6:38 AM

Post #5 of 5 (201 views)
Permalink

Issue 511 in cherokee: trace output timestamps [In reply to]

Comment #4 on issue 511 by binb...@b2host.de: trace output timestamps
http://code.google.com/p/cherokee/issues/detail?id=511

Get rid of a syscall.
Now that sounds really good! :-)

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
_______________________________________________
Cherokee-dev mailing list
Cherokee-dev[at]lists.octality.com
http://lists.octality.com/listinfo/cherokee-dev

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com