From: Wol <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Postfix config and update
Date: Sun, 27 Nov 2022 14:42:03 +0000 [thread overview]
Message-ID: <1e5119ac-8556-fe5f-405b-76dc8e9da197@youngman.org.uk> (raw)
In-Reply-To: <CAC_tCmqMuG_gvtnLm3r62BUnZdVijOCnezXvB_6XybBMOeL1og@mail.gmail.com>
On 27/11/2022 13:21, John Blinka wrote:
> I’m not a systemd user, so I don’t know precisely what systemd does. But
> my /etc/postfix/main.cf <http://main.cf> is a soft link to
> “main.cf.works”, which was an unoriginal name for an experimental config
> file that worked (as opposed to a series of trial configs that didn’t).
> The original main.cf <http://main.cf> is renamed main.cf.orig to keep it
> around as an unadulterated reference. Works for me and doesn’t get
> clobbered in updates.
Systemd stores its *distro*supplied* config files in /usr.
It stores its user-supplied config files in /etc.
So when your distro updates systemd, it doesn't go anywhere near your
local changes.
Dovecot doesn't do it quite the same way, the default distro config
loads a "config.local" file if it exists. So when your distro updates
the master config, your local config is untouched.
Postfix afaik just has one humungous config file, so when your distro
updates the config, all your local changes are trashed :-(
I don't want to faff about with special copies, backups, origs etc.
Everything should "just work (tm)".
Cheers,
Wol
next prev parent reply other threads:[~2022-11-27 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 10:36 [gentoo-user] Postfix config and update Wols Lists
2022-11-27 13:21 ` John Blinka
2022-11-27 14:42 ` Wol [this message]
2022-11-27 22:29 ` John Blinka
[not found] <FwneN-6Fad-1@gated-at.bofh.it>
[not found] ` <FwpTj-6GVn-5@gated-at.bofh.it>
[not found] ` <Fwr8J-6HCU-21@gated-at.bofh.it>
2022-11-27 15:49 ` Mike Civil
2022-11-27 22:12 ` Wol
2022-11-28 23:17 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1e5119ac-8556-fe5f-405b-76dc8e9da197@youngman.org.uk \
--to=antlists@youngman.org.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox