Thanks but that's not a "shortcut".

https://fail2ban.readthedocs.io/en/latest/filters.html#developing-filters
https://github.com/fail2ban/fail2ban/tree/master/config/filter.d

I open this, maybe I will give a try.

Is that possible to hardcode in soju to produce a /var/log/soju.log file ? And add an options in config file, to be able to change the path if needed.

each 30s*

As the freebsd package comes without a service file, I wrote a basic (and dirty) one, which run soju with daemon.

#!/bin/sh

. /etc/rc.subr

name="soju"
rcvar="${name}_enable"
load_rc_config $name
pidfile="/var/run/${name}.pid"

start_cmd="daemon -o /var/log/soju.log -p ${pidfile} /usr/local/bin/soju -config /usr/local/etc/soju/soju.conf"
stop_cmd="/bin/pkill soju && sleep 1"
status_cmd="/bin/pgrep soju"

run_rc_command "$1"

So it produces a soju.log file.

I use monit to periodically test my running services.

check process soju with pidfile /usr/local/bastille/jails/soju/root/var/run/soju.pid
    start program = "/usr/local/bin/bastille start soju"
    stop program  = "/usr/local/bin/bastille stop soju"
    if failed host domain.org port 6697 for 3 cycles then restart
    if changed pid then alert

Problem is that at each port test (which is basically a nc -vz domain.org 6697), it produces a log line. As the test is ran each 120s, I get soju.log flooded by start|end connection lines.

2022/01/06 06:05:14 downstream "192.168.0.254:48654": new connection
2022/01/06 06:05:14 downstream "192.168.0.254:48654": connection closed
2022/01/06 06:05:45 downstream "192.168.0.254:48659": new connection
2022/01/06 06:05:45 downstream "192.168.0.254:48659": connection closed
2022/01/06 06:06:15 downstream "192.168.0.254:48664": new connection
2022/01/06 06:06:15 downstream "192.168.0.254:48664": connection closed
2022/01/06 06:06:46 downstream "192.168.0.254:48673": new connection
2022/01/06 06:06:46 downstream "192.168.0.254:48673": connection closed
2022/01/06 06:07:17 downstream "192.168.0.254:48678": new connection
2022/01/06 06:07:17 downstream "192.168.0.254:48678": connection closed
2022/01/06 06:07:47 downstream "192.168.0.254:48687": new connection
2022/01/06 06:07:47 downstream "192.168.0.254:48687": connection closed

Is that possible to log those only in debug mode ?

On freebsd, blacklistd could filter sasl connections. https://man.netbsd.org/NetBSD-9.2/blacklistd.8

is there a way to sort channels ? At each senpai start, all channels are added in a random order. Alphabetical with auto rearrange when adding a new one ?

I like the way tiny manage this. It underline the first available letter in the channel name and create automatically a shortcut as alt+$letter. It's really specific, but any method is welcome. A fzf-like menu could be cool too.

Ok, I expected that, let's check what my client issue gives. Thanks for answering.

There is something specific to my irc client : tiny-irc-client generates shortcuts as alt+letter relative to the first available letter in the channel name
alt+a leads to #archlinux for exemple
but in single stream mode, all channels are sent in a random order, so all my shortcuts change
in there a way to force the order ?
see -> https://github.com/osa1/tiny/issues/375
a clean solution, would be to store the adding order, and always send channels to this order