Am 28.02.2014 10:02, schrieb WaLyong Cho: > systemd is already provide a special unit. If the type of unit is > service then that is 'basic.target'. Additionally default extra > dependency can be listed in system.conf and then other service unit will > have "After=" dependency implicitly. > In config directory /etc/systemd/default-extra-dependencies, if a > service unit is listed ignore-units or exist symlink in ignore-units.d > then the service units can be launched before extra dependencies.
I am confused about the motivation here. This change adds several extra configuration primitives - one in system.conf, a new directory, and a mechanism to opt out of the new configuration. This is quite a lot for something that I find marginally useful at best. I think this functionality even enables an administrator to unwillingly break his system - setting this option likely has many unforeseen consequences, depending on the installed services. Furthermore, the configuration only affects .service units, but that is not reflected in any of the option names, suggesting it is a configuration that would affect *any* unit. Why should this functionality exist for .service units, but not for others? What's the reason you want to add new dependencies to all units at the same time?
signature.asc
Description: OpenPGP digital signature
_______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
