The longer answer: In the src/support/ directory, you will find a utility called rotatelogs which can be used like this: TransferLog "|/path/to/rotatelogs /path/to/logs/access_log 86400" A more sophisticated solution of a logfile rotation utility is available under the name cronolog from Andrew Ford's site at http://www.cronolog.org/. It can automatically create logfile subdirectories based on time and date, and can have a constant symlink point to the rotating logfiles. (As of version 1.6.

Assuming that you have logrotate installed on your system and is configured to use the /etc/logrotate.d directory for it's configuration files then you can simply create a file, /etc/logrotate.d/denyhosts, edit it and save it. If you have a nonstandard DenyHosts installation then you will need to account for this yourself.

No. HOWEVER, If you are allergic to wheat, and you start eating rice every day, you will most likely become allergic to rice, or any other grain you eat daily.. Repetitive eating is a major cause of food intolerance-eating the same foods day after day after day. That's why wheat, milk, eggs, corn, soy, peanuts, refined sugars and yeast - foods we eat daily - are common allergens. The Rotation Game, Allergy Recipe Book and Calcium without the Cow are excellent examples of rotation diets.

A an access_log entry showing this situation could look like this: 63.251.56.142 - - [25/Jul/2002:12:48:04 -0700] "GET http://www.yahoo.com/ HTTP/1.0" 200 1456 This is usually the result of malicious clients trying to exploit open proxy servers to access a website without revealing their true location. If you find entries like this in your log, the first thing to do is to make sure you have properly configured your server not to proxy for unknown clients.

By default, basic logging is enabled in Webmin. To turn on full logging, go into the Webmin Configuration module, click on the Logging icon and turn on the Log changes made to files by each action option. This will record all file changes and commands run by Webmin. Once logging is enabled, all actions performed from then on can be viewed in the Webmin Actions Log module. Your browser has automatically gunzipped the file for you. Just rename it to webmin-1.400.

The file appender that comes with Log4perl, the Log::Log4perl::Appender::File manpage, will open a specified log file at initialization time and will keep writing to it via a file handle. In case the associated file goes way, messages written by a long-running process will still be written to the file handle. In case the file has been moved to a different location on the same file system, the writer will keep writing to it under the new filename.

Your Web administrator or hosting company should be able to tell you where your log files are located. You will need to enter this information in Web Log DB when you set up a new profile.

Everything in Tk-land is a reference. When defining callbacks take care to pass variables by reference. Callbacks are closures and to ensure a variable gets its current value, as opposed to its value when the callback is defined, pass by reference, e.g.

Our current slideshow template does not allow you to rotate images once they are uploaded into the system. Use a basic program like Windows Picture to rotate your image before uploading it.

If you use the plug-in you can right-click on the image and select Transpose Image, which will allow you to rotate the image. This might be useful on maps that have text written in a variety of orientations. Or for more control (and complexity) you could download the image in .sid format, install the stand-alone viewer, export the image as a .tiff, and import that into your favorite imaging soft (like Photoshop, Paint Shop Pro, etc.) and adjust at will.

The software notifies IIS of the username of each authenticated request, and then IIS will place this info in the IIS configured logfile. Note that with IIS4, by default you will be using W3C extended logging format by default, and you must click on the Properties button, go to the extended properties tab, and enable the Username checkbox. Otherwise usernames will not appear in the log. Refer to your IIS documentation for more details.

Let's assume you wanted to have each logging statement written to a different file, based on the statement's priority. Messages with priority WARN are supposed to go to /tmp/app.warn, events prioritized as ERROR should end up in /tmp/app.error. Now, if you define two appenders AppWarn and AppError and assign them both to the root logger, messages bubbling up from any loggers below will be logged by both appenders because of Log4perl's message propagation feature.