Jason Chu said: > Leaving things the way they are also doesn't help this. Just because the > proposed solution doesn't cover every possible case doesn't mean it isn't > good. It's still an improvement over what currently exists.
A bad solution is not always an improvement over no solution. I think basing a daemon stop order on time is an inherently bad idea. It would make more sense to me to have an alternate designator in the daemons array, that implies that it should not be started by the system...but if it is running at shutdown, it should be stopped.. We have a designator for backgrounding start '@', and for a no start '!'. I would say if we have a '!' in front of a daemon, we should check to see if it is running at shutdown (by checking it's entry in the /var/run dir) and then simply stop it. It would then still be up to the user to set the start/stop order. I was just concerned about relying on a timestamp, not simply disregarding the usefulness of such a thing. _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
