Weekend Data Log


 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers Weekend Data Log
# 1  
Old 09-02-2008
Weekend Data Log

I've been searching here, and other places for a solid script that would generate a weekend log. Mainly how would I combine 24hr data for the weekend days? I've came across scripts for day, days, month, but none that selects just the weekend. Thanks for any help!
 
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Linux

power off during weekend

Hello, I would like to turn off (mean no energy consumption) some servers during the weekend. I would like to do it automatically so i thought to create macro commands to a shell client.The problem is that giving shutdown (shutdown -h now) the server(Sun X4200 M2) turn off but the fans are still... (5 Replies)
Discussion started by: @dagio
5 Replies

2. What is on Your Mind?

what are you doing this weekend?

does someone have any plans? (7 Replies)
Discussion started by: yarx
7 Replies
Login or Register to Ask a Question
make_combined_log.pl(1) 				      General Commands Manual					   make_combined_log.pl(1)

NAME
make_combined_log.pl - make combined logfile from SQL database SYNOPSIS
make_combined_log.pl <days> <virtual host> DESCRIPTION
This perl script extracts the httpd access data from a MySQL database and formats it properly for parsing by 3rd-party log analysis tools. The script is intended to be run out by cron. Its commandline arguments tell it how many days' worth of access records to extract, and which virtual_host you are interested in (because many people log several virthosts to one MySQL db.) This permits you to run it daily, weekly, every 9 days -- whatever you decide. NOTE
By "days" I mean "chunks of 24 hours prior to the moment this script is run." So if you run it at 4:34 p.m. on the 12th, it will go back through 4:34 p.m. on the 11th. KNOWN ISSUES
Because GET and POST are not discriminated in the MySQL log, we'll just assume that all requests are GETs. This should have negligible effect on any analysis software. This could be remedied IF you stored the full HTTP request in your database instead of just the URI, but that's going to cost you a LOT of space really quickly... Because this is somewhat of a quick hack it doesn't do the most robust error checking in the world. Run it by hand to confirm your usage before putting it in crontab. AUTHOR
Edward Rudd <eddie@omegaware.com> MAN PAGE CREATED BY
Michael A. Toth <lirul.lists@gmail.com> - based on comments of script COMMENTS
This man page was written using xml2man (1) by the same author. Manuals User make_combined_log.pl(1)