Quassel IRC

h1. Quassel Logging

{{toc}}

Quassel saves all logs into the database, it never forgets backlogs unless you delete a buffer. You can either scroll back in chat windows as far as you like, or you can use a tool to dump or view the logs in plaintext format.

h2. Tools

h3. dumplog

this tool (written in Python) dumps quassel logs to a file. Currently it exports mIRC format.

You can get it at

> attachment:dumplog-0.0.1.tar.gz

it is rather self-explanatory, telling you if something went wrong. you can run it with

*default database path (ok for most unixes)*

<pre>python dumplog.py -u username -n network -c "#channel" -o channel.log</pre>

*custom database path (Windows etc.)*

<pre>python dumplog.py -d "C:\Quassel\quassel-storage.sqlite"</pre>

**Examples:**

>*show users in quasseldb*

><pre>python dumplog.py</pre>

>

>*show networks for quassel user john*

><pre>python dumplog.py -u john</pre>

>

>*show channels for network Freenode for user john*

><pre>python dumplog.py -u john -n Freenode</pre>

>

>*dump channel #quassel on network Freenode for user john to file quassel.log*

><pre>python dumplog.py -u john -n Freenode -c "#quassel" -o quassel.log</pre>

*Limitations / Known Issues*

dumplog currently only handles sqlite databases, postgres shouldn't be too hard if requested though.

nasty charset conversion takes place, gonna be fixed soon

topics will only be properly parsed with English logs, need to talk with Sput/EgS about that ;P

*Note*

this tool is not maintained by quassel staff, contact Gentle on Freenode for bugs or feature requests

h3. quasselsuche

A webbased Quassel-Search-Engine for Quassel IRC

!quassel_backlog_search.png!

*Download*

Snapshots and git version tracker can be found here: http://m4yer.minad.de/quassel/

*Note*

this tool is not maintained by quassel staff, contact m4yer on Freenode for bugs or feature requests

h3. Windows - Portable quasselsuche

This is the same quasselsuche as above, pre-packaged for Windows with a web server ("mongoose":https://github.com/valenok/mongoose) and php. Just "extract":http://7-zip.org and *run start-search-server.bat*. No install required and no traces are left outside the extracted directory. Further info and instructions are available at readme.txt in that package.

* Note - If you don't know your username/password, run show-password.bat

*Download*

Current version is 1.1 (updated 2012-08-19): "portable-quassel-backlog-search-v1.1.7z":http://share.minad.de/mtUC.1.7z

* Note - The above package is 9 MB since it includes php. If you already have a local copy of php (zipped package for windows), you can download a smaller package (180 KB) to which you would need to extract php yourself: "portable-quassel-backlog-search-v1.1-NO-PHP.7z":http://share.minad.de/1phm.1-no-php.7z

*Note*

this tool is not maintained by quassel staff, contact Avi Halachmi (avih on Freenode) for bugs or feature requests

h3. Quasselsearch

With this bash script you can search your quassel database from the command line and get the output as a csv file/right in your terminal. You can get the script at "github": https://github.com/karan42/quasselsearch 

Requirements: Gnu awk, sqlite3 backend

How to use: Add yourself to the group "quasselcore" and then just run the script normally by doing "./quasselsearch <options>"

The available options are : 

Usage : quasselsearch.sh (n|c|t|e|s|o|q|d|f)

-n nick 

-c channel

-t start date in the format "YYYY-MM-DD HH:MM:SS" 

-e end date in the same format as above

-s search term 

-o output file 

-q quassel user defaults to $USER 

-d quassel database location , defaults to /var/lib/quassel/quassel-storage.sqlite

-f Change the time format, all formats that are accepted by the "date" command are allowed.

All the arguments are optional. Although if you run it without any arguments you would print out your whole backlog from all buffers. 

Example:

><pre>./quasselsearch.sh -n karan -c #quassel -t 2015-04-20 -e 2015-04-30 -o logs.txt -s quasseldroid </pre>

*Note*

this tool is not maintained by quassel staff, use the github page for bugs or feature requests

*Note* 

Since the tool uses sql to extract stuff, it could possibly work on postgresql cores too, if you do give it a try please inform me at karan 90 at g mail.c om (no spaces) so i can update the code. Thanks.