as a result of the discussion in this thread i have now removed rsyslog from the core snap for ubuntu-core images in the edge channel (available with the next build of the core snap that is currently running).
this will avoid duplication of services, extensive writes to solid state disks (less wear-out) and in general the waste of disk space for log files.
we are left with journald on our images which logs to a ringbuffer by default, some notes and hints:
- if you want persistent logs across reboots, create the /var/log/journal directory, journald will start writing its log blobs to this dir then (a config option will later be added to the core snap to toggle this behaviour on/off)
- remote logging is currently not available out of the box but there is still an open item wether we want to ship systemd-journal-remote in the image (and have configure options for it)
- an rsyslogd snap will be created for users that perfer rsyslog
if you want to test the new logging behaviour you can switch your test device to the edge channel via:
snap refresh core --edge
to go back to stable:
snap refresh core --stable
this change will come to stable earliest in 4 weeks. in case you run into any issues with your snaps or device setup, please speak up in this timeframe.