W3C home > Mailing lists > Public > www-jigsaw@w3.org > May to June 1996

Re: Logfile Suggestions

From: Mark Friedman <mark@intraspect.com>
Date: Thu, 27 Jun 1996 09:09:44 -0700
Message-Id: <31D2B248.4655@intraspect.com>
To: Anselm Baird-Smith <abaird@w3.org>
Cc: Doug Marker <dmarker@zeta.org.au>, www-jigsaw@w3.org
Forgive me for the funked up mail that I sent yesterday. Something went 
kablooey with my mailer. What I meant to say was:

I wonder if Doug's problem is related to my complaint about the apparent
non-flushing of logfile buffers. 

-Mark

Anselm Baird-Smith wrote:
> 
> Doug Marker writes:
>  > One suggestion we want to offer is that the log file not be locked to
>  > prevent other tasks or processes reading it.
>  >
>  > In our other servers we were able to write simple & quick scripts that
>  > would allow us to glance through the log each to to check activity. With
>  > Jigsaw we can't get at the log unless we shutdown Jigsaw then we can
>  > view the file.
> 
> I am not sure what you mean by locking (?) If you take a look at the
> w3c.jigsaw.http.CommonLogger, you will see that it just uses a
> RandomAccessFile to output the log (arent' you hitting an OS/2
> specificity ?)
> 
>  > In time we could write a resource to display it on-line (is there one ?)
> 
> This ought to be part of the "monitoring" part of what should be a
> jigadm application, probably based on applets.
> 
> Anselm.
Received on Thursday, 27 June 1996 12:09:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:25 GMT