make_combined_log.pl(1)
π make_combined_log.pl(1) π
okay bestie, buckle up, this is the make_combined_log.pl manual β a General Commands Manual situation, and it's giving extremely useful chaos. let's go π¦
β¨ NAME β¨
make_combined_log.pl β make combined logfile from SQL database. yes that's the whole vibe. logfile. from SQL. combined. slay π
πΈ SYNOPSIS πΈ
make_combined_log.pl <days> <virtual host>
two args, that's it, iconic. π
π DESCRIPTION π
so this perl script goes into a MySQL database, pulls out the httpd access data, and formats it properly so that 3rd-party log analysis tools can parse it. it's giving "translator between two worlds" honestly π
the script is meant to be run out by cron. its commandline arguments tell it:
- how many days' worth of access records to extract
- which virtual_host you're interested in
(that second one matters bc many people log several virthosts into one MySQL db, and we are NOT about to mix them up, no ma'am π)
and the best part? this means you can run it daily, weekly, every 9 days β whatever you decide. your schedule, your rules, main character energy fr fr β¨
β NOTE β
when we say "days" we mean "chunks of 24 hours prior to the moment this script is run."
so likeβ¦ if you run it at 4:34 p.m. on the 12th, it will go back through 4:34 p.m. on the 11th. it's not "midnight to midnight", bestie, it's exactly 24 hours before right now. clock math, not calendar math. π
π KNOWN ISSUES π
okay so here's where we keep it real:
- 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. it 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β¦ like, a lot a lot. π
- because this is somewhat of a quick hack, it doesn't do the most robust error checking in the world. so likeβ¦
π¨ bestie please β run it by hand to confirm your usage before putting it in crontab. do not rawdog this into a cron job. i'm begging. π«Ά
π AUTHOR π
Edward Rudd <eddie@omegaware.com>
π§ MAN PAGE CREATED BY π§
Michael A. Toth <lirul.lists@gmail.com> β based on comments of script. a real one for this. π
π COMMENTS π
this man page was written using xml2man (1) by the same author. yes, the man page about the script was made by the same person as the script-adjacent stuff. it's giving full-circle. we love to see it. π
and that's the whole page, bestie!! this lil gem comes to you from the Manuals collection, sitting in the User section, and its official name-tag is make_combined_log.pl(1). go forth and combine those logs. periodt. ππ¦β¨
π¦ where this page comes from
- debian bookworm: libapache2-mod-log-sql 1.100-16.3+b1 Β· mod-log-sql
- debian trixie: libapache2-mod-log-sql 1.100-16.4 Β· mod-log-sql
- ubuntu jammy: libapache2-mod-log-sql 1.100-16.3build2 Β· mod-log-sql
- ubuntu noble: libapache2-mod-log-sql 1.100-16.3build4 Β· mod-log-sql
- ubuntu questing: libapache2-mod-log-sql 1.100-16.4build1
- ubuntu resolute: libapache2-mod-log-sql 1.100-16.4build2 Β· mod-log-sql
- ubuntu stonking: libapache2-mod-log-sql 1.100-16.4build2 Β· mod-log-sql
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms