Switch to s6-overlay, add cron (and cronjobs), syslog.

README.md

@@ -26,6 +26,7 @@ services:
       - "./data/run:/inn2/run"
       - "./data/spool:/inn2/spool"
       - "./data/tmp:/inn2/tmp"
+      - "./data/syslog:/var/log"
     ulimits:
       nofile:
         soft: 65535
@@ -47,6 +48,7 @@ services:
       - "./data/run:/inn2/run"
       - "./data/spool:/inn2/spool"
       - "./data/tmp:/inn2/tmp"
+      - "./data/syslog:/var/log"
     networks:
       inn2-ipvlan:
         ipv4_address: 192.168.168.168 # ip address from real LAN.
@@ -81,10 +83,12 @@ Note that this code is built to support dual-stack (IPv4+IPv6). You should eithe
 
 ## Cronjobs
 
-There is a section in documentation about cron jobs you should configure. This docker image currently isn't supporting these, so configure it separately with lines like:
+This Docker image come with a recommended in documentation set of cronjobs. To customize it copy `etc/crontabs/news` file, make neccessary changes and mount it to container in `/etc/crontabs/news`.
+
+If you want to use cron outside of your container:
 
 ```shell
-0 3 * * * docker compose run inn news.daily expireover lowmark
+0 3 * * * docker compose run inn news.daily expireover lowmark delayrm
 ```
 
 ## Sending emails
@@ -115,3 +119,14 @@ inn2 is launched as UID/GID 600 in container, so chown directories properly acco
 
 * If you're not using userns isolation - use `chown 600:600`.
 * If you're using it - use `600 + id from /etc/subuid`, e.g. if you're using default Docker remapping this could be `chown 100600:100600`.
+
+## Logs
+
+Logs are split in two destinations:
+
+* `/inn2/log` - default INN logs destination.
+* `/var/log` - syslog logs.
+
+As INN might log in both of them you should mount a directory for each.
+
+For syslog logs it is a known bug that logs isn't written in `/var/log/innd` or `/var/log/nnrpd`, take a look at `/var/log/syslogd/everything/current` for logs with `news` topic. This might be fixed somewhere soon.