Andras Korn <korn-debb...@elan.rulez.org> writes: > I began using a revision tracking system for some configfiles. This > involved replacing /etc/nullmailer with a symlink to a directory > within the local working copy.
I don't know if it's practical for you, but as a workaround etckeeper works fine with the current nullmailer, since it doesn't use symlinks. > Also, printing messages to /dev/console isn't terribly useful in the > case of remote headless servers. I don't (yet) see what is explicitely opening /dev/console. How are you starting nullmailer? For example, I would expect systemd to capture stdout. Although README.Debian mentions /dev/console, this patching to change upstream's logging is no longer done in the current version of nullmailer. > 1. in order to avoid violating the principle of least surprise, don't > disregard /etc/nullmailer/me. If it's there, the admin put it there > for a reason. I would have to go back and read the (ancient) bugs for why this change was made in the first place. I guess allowing /etc/nullmailer/me to override /etc/mailname will break some existing configurations. > 2. if /etc/nullmailer/me doesn't exist, default to "/etc/mailname", > not "/etc/nullmailer/../mailname". Offhand I don't understand why it doesn't use an absolute path there. Maybe someone (tm) can change the appropriate line in hostname.cc and test the result.
