They each end with a `SUCCEEDED` or `FAILED` message.
### One bit of awkwardness
### Summing this all up:
I find it most meaningful to run the `slapd` and `radiusd` daemons, which respond to the `radiusclient`, in their own terminal window. That way, when you run `radiusclient` in its window, you can see that status and any error messages in a side-by-side fashion.
I find it most meaningful to run the `slapd` and `radiusd` daemons, which respond to the `radiusclient`, in their own terminal window. That way, when I run `radiusclient` in its window, I see any status and error messages in a side-by-side fashion.
But it is here in the radiusclient/makefile that the certificates get generated and installed. And they have to be in place *before*`slapd` and `radiusd` are launched.
