16:06 < codept> is there any tool to ...like ...present logs in the /var/log
...in more simpler format, let say httpd-access.log, a tool
that can analyze it and gives number of connection for each
unique source, ...that is just an idea
16:10 < geek00l> codept, we call it - awk, sed, sort, uniq, grep and fuck

Be Gentle With Your Keyboard

I just learn that, (after years of facing terminal), the more you minimize your typing mistakes, lesser the potential of screwing up or end up your work dissatisfied. It helps me thinking better too.

Think before you type. Think again before you press enter. Avoid typing too fast (because there are kids who think typing fast shows that they're good). Type slow not too slow, sit back and relax. Enjoy the cleanliness of your terminal output.

p/s: Yeah, I've worked with business critical environment... and I did screw up a few times :-p And this came to my mind while I was watching a 'really good' but not sys admin guy, typing neatly.

Start postgresql, create database and access it

Platform:FreeBSD

# su - pgsql
$ initdb -D /usr/local/pgsql/data (if only doesn't exist)
$ postgres -D /usr/local/pgsql/data >logfile 2>&1 &
$ createdb test
$ psql test

Install: using ports
Binary location: /usr/local/bin
Don't forget to modify rc.conf

httpd.conf | php module

beside LoadModule php5_module libexec/apache22/libphp5.so



Edit Aug 12 2008:
AddType application/x-httpd-php .php
AddType application/x-httpd-php-source .phps