Hello, Gabriel. On Mon, 2025-08-04 at 02:34 +0200, Gabriel Wicki wrote: > sudo herd status dovecot > shows no logging messages, and neither /var/log/messages nor > /var/log/mail.log contain anything meaningful (except shepherd's > service > started & service stopped messages in the former). > > are you running your instance with the default configuration?
I did have a few messages. But those were error messages from the dovecot service itself about contradictions in my dovecot configuration. You are right, I do not see the normal logs from docecot there by default. The guix manual currently says that the default value for "dovecot- configuration" parameter "log-path" is "syslog". This means that dovecot attempts to use syslog for logging by default. However, I remember that shepherd took over logs from syslog in the default configuration earlier this year. So, I suppose that those messages go nowhere when the value is "syslog". I changed the value to "/dev/stderr", which is the other value suggested in the guix manual, like this: > (service dovecot-service-type > (dovecot-configuration > (log-path "/dev/stderr") > ...)) I can see the messages now. I assume that shepherd reads the messages from standard output and standard error of the services. So, it did not show anything because dovecot was trying to direct the messages directly to syslog instead. The following command opens the relevant part of the guix manual for me. $ info guix log-path Roman
signature.asc
Description: This is a digitally signed message part
