Sponsorised links
September 2008
apache-scalp - Google Code
by camel
(via)
Scalp! est un analyseur de logs Apache qui sert dans la recherche de problèmes de sécurité et de tentatives d'intrusions, il est basé sur des requêtes du même style que celles du utilisées dans le projet PHP-IDS
August 2008
IE WebDeveloper - DOM Inspector, Script Console, Logging messages and HTTP Monitor
by camel
IE WebDeveloper is an add-on for Microsoft Internet Explorer. The rich web debugging toolset allows you to inspect and edit the live HTML DOM and current cascaded styles, evaluate expressions and display error messages, log messages, explore source code of webpage and monitor DHTML Event and HTTP Traffic.
Sponsorised links
July 2008
June 2008
Splunk > Download Splunk 3.2
by camel
Splunk is IT Search. Search, navigate, alert and report on all your IT data in real time. Logs, configurations, messages, traps and alerts, script, code, metrics and more. If a machine can generate it -- Splunk can eat it.
wtop - Google Code
by camel
& 1 other
wtop is really cool application for web server log analysis and to see server stats at a glance. It also has powerful log grepping capability. It is just like 'top' for your webserver.
It can find out number of searches or signups per seconds. It can also create histogram of response time. There is also another tool called logrep a powerful command-line program for ad-hoc analysis and filtering for log files. You can dig up lots of information using wtop tools.
Multitail, le tail ultime ?
by camel
C’est en parcourant le dernier numéro hors série de Linux Magazine que je suis tombé sur un article sur un outil qui peut changer la vie des administrateurs systèmes. Cet outil s’appelle Multitail et est présenté par son concepteur (Folker Van Heusden) comme un “tail sur stéroides”.
Comme moi, vous devez avoir en permancence plusieurs “tail -f” lancée en // pour surveiller les logs de vos serveurs. Multitail propose de réunir toutes ces informations dans une seule et même fenêtre.
May 2008
April 2008
Logmonster FAQ - The Network People, Inc.
by camel
Typical Scenario: You have a web server that serves your domain. You write a simple script to restart apache each night and pipe the logs off to your analyzer. It works.
ISP/Hosting Scenario: Each server hosts many domains. You may also have load balanced servers (multiple machines) serving each domain. A tool like this is necessary to:
1. collect all the log files from each server
2. split the logs based on the virtual host(s)
3. discard invalid entries (phishing, referrer spam, etc)
4. sort them into chronological order
5. feed logs into analyzer
6. do something with the raw logs (compress, save to vhost dir, etc)
[edit]
Advanced Logging Techniques With Apache
by camel
Logs in Apache are more configurable than most people realize. Not only can you organize the fields in your logs, but you can also create formats and layouts. Access logs can be split and divided up to make them easier to process by reporting specific items or ignoring those items that have no relevance.
March 2008
BSDspot » Getting Awstats to Work with Qmail
by camel
To get awstats to work with qmail log files I use this little script from Bob Hutchinson called qlogs4awstats.
February 2008
Simple SSE optimized sin, cos, log and exp
by ogrisel
I chose to write them in pure SSE1 MMX so that they run on the pentium III of your grand mother, and also on my brave athlon-xp, since thoses beast are not SSE2 aware. Intel AMath showed me that the performance gain for using SSE2 for that purpose was not large enough (10%) to consider providing an SSE2 version (but it can be done very quickly).
The functions use only the _mm_ intrinsics , there is no inline assembly in the code. Advantage: easier to debug, works out of the box on 64 bit setups, let the compiler choose what should be stored in a register, and what is stored in memory. Inconvenient: some versions of gcc 3.x are badly broken with certain intrinsic functions ( _mm_movehl_ps , _mm_cmpeq_ps etc). Mingw's gcc for example -- beware that the brokeness is dependent on the optimization level. A workaround is provided (inline asm replacement for the braindead intrinsics), it is not nice but robust, and broken compilers are detected by the validation program below.
January 2008
dlog - log file analyzer for qmail, dnscache, tinydns, rbldns, axfrdns, publicfile and qpsmtpd
by camel
A log file analyzer for qmail, dnscache, tinydns, rbldns, axfrdns, publicfile and qpsmtpd.
Zork[Yy]'s log : Connaissez-vous qpsmtpd ?...
by camel
& 1 other
qpsmtpd est un serveur SMTP très léger et très modulaire qui se base sur le principe des plugins et des hooks qu’il peut appeller à chaque instant du protocole SMTP : mail from, rcpt to, data, ... Le principe est de lancer qpsmtpd à l’écoute du port SMTP (25), charge à lui ensuite de faire les vérifications d’usage (beaucoup de plugins sont livrés dans le produit de base pour ce type d’opérations) pour ensuite relayer au serveur de messagerie qui écoutera sur un autre port (2525) par exemple. En gros qpsmtpd joue le rôle de firewall ou de frontal mail avant d’entrer dans l’infrastructure de la messagerie interne.
L’avantage de cette technique est de pouvoir développer un plugin maison, avec des hooks à appeler selon ses besoins : on peut introduire des règles métiers sur les mails : vérification de l’existence du compte, vérification de l’expéditeur selon des règles qui nous sont propres, etc…et de couper la transaction SMTP avant même de recevoir le message : gain de temps et de ressources pour le serveur MTA en bout de chaîne.
December 2007
