Omar Polo <o...@openbsd.org> writes: > Hello ports, > > after net/pounce here's litterbox too :) > > nadeshiko$ pkg_info litterbox > Information for inst:litterbox-1.8 > > Comment: > TLS-only IRC logger > > Description: > litterbox is a TLS-only IRC logger. It logs events from IRC in a > SQLite database, indexing messages for full-text search. It is > intended for use with the IRC bouncer pounce, but can also be used > independently as a logging bot. > > Maintainer: Omar Polo <o...@omarpolo.com> > > WWW: https://git.causal.agency/litterbox/about/ > > > To use it the database must be initialised first with `litterbox -i', > but there's a catch: if ~/.local/share doesn't exists litterbox fails. > > nadeshiko$ litterbox -i > litterbox: /home/op/.local/share/litterbox/: No such file or directory > litterbox: database not found; initialize it with litterbox -i > nadeshiko$ mkdir -p .local/share > nadeshiko$ litterbox -i > nadeshiko$ echo $? > 0 > nadeshiko$ > > The first message is quite clear, while the second not so much; > otherwise works fine with pounce on i386. (If I don't forget I'll > report this upstream.) > > Later, the database can be queried with scoop(1), which has a fairly > powerful filtering abilities. There's also a web UI called scooper[0] > that's built with kristaps' kcgi, but I've not tried it yet (and I'm not > that interested in querying my IRC logs with a web browser :P) > > Just as pounce, the program doesn't daemonize itself and it stops if the > connection fails. The author suggests to run it with catsit, which is a > supervisor that automatically restarts the processes when they fail. I > don't really like the idea and I'm not sure whether we want to encourage > auto-restarting failed services, so I'll keep it in a while loop inside > a tmux session like I do with pounce ;) > > OK/comments/feedbacks? > > [0]: https://git.causal.agency/scooper/about/
now with a correct license marker: it's GPLv3+ (thanks sthen@)
litterbox.tar.gz
Description: Binary data
