| 1 |
On Tue, Oct 28, 2014 at 9:36 PM, Tom H <tomh0665@×××××.com> wrote: |
| 2 |
> Since Gentoo's rpcbind.service has "Wants=rpcbind.target" and |
| 3 |
> "Before=rpcbind.target"", having nfs-server.service depend on |
| 4 |
> rpcbind.target rather than rpcbind.service should work as long as |
| 5 |
> rpcbind.service is enabled. |
| 6 |
> |
| 7 |
> But having "Requires=rpcbind.service" and "After=rpcbind.service", |
| 8 |
> like nfsd.service has/had, means that you don't have to enable |
| 9 |
> rpcbind.service. |
| 10 |
> |
| 11 |
|
| 12 |
I was just looking at that and thinking the same thing. Nothing is |
| 13 |
really forcing rpcbind to load the way things are specified right now. |
| 14 |
If a service really requires another service to operate, it should say |
| 15 |
that. There is no problem doing that via a target, but then the |
| 16 |
target still needs to pull it in. |
| 17 |
|
| 18 |
There seems a general tendency in systemd to express dependencies as |
| 19 |
"after" instead of "requires." That is fine if the service doesn't |
| 20 |
really require something else, but if there really is a true |
| 21 |
dependency then it just causes problems when somebody doesn't notice |
| 22 |
and fails to enable the other unit. |
| 23 |
|
| 24 |
-- |
| 25 |
Rich |
Archives