Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 170258 - etc-update doesn't follow symlinks
Summary: etc-update doesn't follow symlinks
Status: RESOLVED WONTFIX
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core - Configuration (show other bugs)
Hardware: All Linux
: High enhancement
Assignee: Portage team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-10 12:59 UTC by CPUShare
Modified: 2007-06-05 23:27 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
follow symlinks while searching .cfg000 files (z,606 bytes, patch)
2007-03-10 13:00 UTC, CPUShare
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description CPUShare 2007-03-10 12:59:51 UTC
I noticed I had some .cfg00 file in /etc/postfix that wasn't detected by etc-update. The reason was that I keep my while email system encrypted on disk, including the smtp ssl keys, and /etc/postfix is actually a symlink that points to the encrypted mount. I will attach a patch that seem to resolve the problem.

Reproducible: Always
Comment 1 CPUShare 2007-03-10 13:00:35 UTC
Created attachment 112792 [details, diff]
follow symlinks while searching .cfg000 files
Comment 2 Marius Mauch (RETIRED) gentoo-dev 2007-06-05 18:05:28 UTC
Hmm, this could be quite annoying if a package installs a symlink from /etc to /usr (like apache or xorg used to do) and installs many files into the symlink location.
Anyone else having an opinion on this one?
Comment 3 CPUShare 2007-06-05 20:35:38 UTC
I guess it could be a problem for things like /etc/spamassassin if something (duplicate _cfg entries would be returned). Perhaps I should use mount --bind instead of a symlink. The symlink looked more strightforward though...
Comment 4 CPUShare 2007-06-05 23:27:28 UTC
ok, given this wasn't an obvious approach, never mind, I solved it by moving the sensitive private keys out of /etc/ and by symlinking the private keys directly instead of pretending to migrate the entire directory to a crypto partition.

Thanks.