On Mon, 24.03.14 14:00, Michael Biebl ([email protected]) wrote: > Don't parse Red Hat style chkconfig headers if chkconfig support is > disabled via --disable-chkconfig.
Hmm, I am not overly hapy with adding even more ifdefs to the code... i'd rather see less ifdefs... Thus, what's the rationale here? Why shouldn't the chkconfig header be read when it exists? I mean, stuff like the description string really shouldn't hurt on debian either, should an init script carry the header... Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
