Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 13400] symlinks for config files should not be reaped

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT bugs.sourcemage.org
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 13400] symlinks for config files should not be reaped
  • Date: 25 Feb 2007 20:44:16 -0000

http://bugs.sourcemage.org/show_bug.cgi?id=13400





------- Additional Comments From sobukus AT sourcemage.org 2007-02-25 14:44
-------
Well, there was no actual loss of data, but the LDAP config was broken and
thus all user (except root) authentification on the system using pam_ldap and
nss_ldap.
It is unnecessary breakage and I really hope it is fixed some time.
Until then, I guess my friend will resort to just not touching that install
and not updating. His experience now is that when you update, things break -
even when you monitor the update and ask all questions with thought.
I hoped to convince him to use SMGL also to have a way to have updates
managed
(to be done at all)... perhaps I'm to eager in that care for one potential
(and capable) supporter.

And my patch... it was the simplest resolution that occured to me. As I don't
see a point in treating symlinks any differently at all, I didn't try to.
There may be a reason... but this function just deletes all the stuff.
The only change now is that the symlinks are considered to be possible config
files where they all were deleted right away before.
I don't quite understand your concern

> It treats *all* symlinks to files as files,
> whether or not they're config files or not.

rm -f does the same for a symlink or a file ... indeed, my point is to drop
the distincion; check symlinks and files for being config files and delete if
not. The patch could be cleaned up for that, but the effect would be the same.
Either we treat symlinks to files differently or not. I don't see the point
where you could limit the treatment and not treat '*all*' file sylmlinks the
same.

Anyway, perhaps someone remembers why the code treats the symlinks
differently... or we find a reason... or we change it.

--
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page