Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 5649] stable sorcery's dispel no longer removes initscripts when a spell is removed

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT metalab.unc.edu
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 5649] stable sorcery's dispel no longer removes initscripts when a spell is removed
  • Date: Fri, 13 Feb 2004 21:32:14 -0500

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





------- Additional Comments From charkins AT pobox.com 2004-02-13 21:32 -------
After thinking more about this, its probably not worth considering the effects
this has on using the cache files on the iso and such. There are other, more
significant, problems with doing that, so it will have to be post-1.0.

The concern is how this effects the existing sorcery system. There were two
main
problems from my point of view:

1) Not tracking the init scripts caused the scripts not to be removed on
dispel.
This could result in users seeing various failed messages on boot because
these
scripts were still enabled. If the user removed the script (to avoid the
failure
messages) and later resurrected the spell, there would be no init script.

Tracking the scripts mostly solves this problem, though the enabled/disabled
state of the init script upon resurrecting will be the same as when the spell
was cached, not the state when the spell was dispelled.

Another possible approach to this would be to not archive the init.d scripts
and
xinetd scripts, but instead re-query xinetd/init.d upon resurrecting.

2) The other issue is with the remaining scripts from init.d that are not
being
tracked. Not considering the philisophical reasons for tracking everything
for a
spell, the only potential problem I see with this is if one of the scripts
needs
to be removed in future versions of the init.d system. If these were tracked,
it
would happen automatically.





------- 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