At 11:51 PM 5/10/2005, André Malo wrote:
. builds and the old tid:time:pid format is good still on unix.
What happend to the good ol' RTC?
shrug happy to revert it. mod_log_forensic certainly isn't in
the --modules-most list - and was a typical example of an explicitly
thread-unsafe module.
On Tue, 10 May 2005 23:36:57 -, [EMAIL PROTECTED] wrote:
[...]
+const char * get_forensic_id(pool *p)
+{
+static APACHE_TLS next_id = 0;
+
+/* we make the assumption that we can't go through all the PIDs in
+ under 1 second */
+#ifdef MULTITHREAD
+return ap_psprintf(p,
At 08:39 AM 5/11/2005, Brian Havard wrote:
On Tue, 10 May 2005 23:36:57 -, [EMAIL PROTECTED] wrote:
+#ifdef MULTITHREAD
+return ap_psprintf(p, %x:%lx:%x, getpid(), time(NULL), next_id++);
+#else
+return ap_psprintf(p, %x:%x:%lx:%x, getpid(), gettid(), time(NULL),
next_id++);
+#endif
At 06:36 PM 5/10/2005, [EMAIL PROTECTED] wrote:
Win32-enable, unix threaded-enable the mod_log_forensic module.
* adds a get_forensic_id() function, differing between win32,
threaded, and non-threaded platforms (threaded and win32
platforms get instead an pid:tid:time:seq
* William A. Rowe, Jr. wrote:
Thanks for catching that, but...
I'm very interested for someone(s) to verify that
. it works on netware?
. builds and the old tid:time:pid format is good still on unix.
What happend to the good ol' RTC?
nd
--
Wenn nur Ingenieure mit Diplom programmieren
