On Tue, 02.12.14 10:30, Flavio Leitner ([email protected]) wrote: > Sort of. This special restart is only need on few cases when > hot-upgrading, otherwise users expect full restart which is already > accomplished by the current service unit. > > It seems to me that the solution is a mix of making two units and wrap > the special upgrade in a separate script which would manage each > daemon properly. Does that make sense to you? > > I am worried with the usability too, because I don't want the admin to > worry about each daemon. I would rather have a single unit > controlling both at the same time. It might be possible to have this > 'front-end' unit to be one of the daemons and make it work as you > described in (b) using Requires=. > > I will do some experiments later on.
You can also create a "target" unit that combines both units into one. Call it "openvswitch.target" make it pull in your two service units, and then add PartOf= dependencies from them back to the target. Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
