No need to apologize. You tried to teach me something and I was too dense to understand. Now I get it and am grateful for the lesson.
> On Dec 17, 2024, at 19:00,m...@cappella.us <mailto:m...@cappella.us> wrote: > > Apologies. No need to do any of that. Instead ... > >> says to override default variables by putting them in the following file: >> >> /etc/logwatch/conf/logwatch.conf >> >> However, that directory does not exist. So, I'm lost. Do I need to create >> that directory or does the override file go somewhere else? > > You'd do this: > > sudo mkdir -p /opt/local/etc/logwatch/conf > sudo touch /opt/local/etc/logwatch/conf/logwatch.conf > > Edit that file as root to add your overrides. > On Dec 17, 2024, rlha...@smart.net <mailto:00rlha...@smart.net> wrote: > Together with the prior "re-root" comment, that means instead of copying the > file to /etc/logwatch/conf and editing it as desired, it should be put in > /opt/local/etc/logwatch/conf. > > Further consideration of the comments means that almost always, a MacPorts > port would put files in /opt/local/etc/... that would normally go in > /etc/....; ditto for /opt/local/var vs /var, and so on. Likewise, things that > non-MacPorts installs of software that usually installs in /usr/local/... > would tend to install in /opt/local/... There might be slight variations or > exceptions, but if you check those, you'll usually find the answer.. Got it. I knew that MacPorts installed binaries in /opt/local/bin but had no idea that other files went to /opt/local/etc/. I have only a few ports installed, so perhaps that’s why I never ran into this before. I appreciate the explanation.
smime.p7s
Description: S/MIME cryptographic signature
