On Mon, 24.03.14 19:04, Michael Biebl ([email protected]) wrote: > > > We could probably just drop the priority info parsing entirely, since it > > is pretty useless these days: as no native units carry a priority number > > we cannot make any useful use of the chkconfig priority anyway > > anymore... It is only useful to order sysv scripts with such a number > > against other sysv scripts with such a number, but not against any other > > service... > > > > Hence, given it is broken/useless already, if we drop that specific part > > of chkconfig support entirely, would that be enough for your issue as > > well? > > See the bug report I posted earlier. > The discrepancy between the chkconfig head and the LSB header (the > latter being the correct one) caused a dependency loop and ultimately > dbus.socket to be dropped.
So this is about the priority number and nothing else? If so, then I am happy to take a patch that drops taking the chkconfig priority number into account entirely, while leaving the rest of chkconfig parsing in there, unconditionally. That should fix the immediate bug you are encountering, right? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
