This is splorp.

ISSN 1496-3221

|

August 23, 2002

The missing links.

It was news to me, but it explained more than a couple of gaps in my server statistics over the past few months. Apparently, when you copy a WebStar log file using FTP, WebStar thinks the file is busy during the session and stops writing to it. This would be fine as long as WebStar resumed logging to the file after the FTP session was completed. Well, it doesn’t. I had copied a week’s worth of log files, including the current log, in order to crunch through and locate a recent burst of referral traffic. When I copied the current file, WebStar silently objected, suspended logging, and left me with a partial record of the traffic for that day. I found out on my own that if you manually suspend and activate logging using the remote admin, WebStar will start writing to the file again. This solution is documented in the WebStar Knowledgebase, but just barely. I’m still running version 4.x on this machine, so I can’t say whether or not this occurs with the most recent release as well. Just one more thing to file under “quirky application behavior” I suppose.

This item was posted by Grant Hutchinson.

Categories:

Comments are closed.

|

Comments are closed.