Hi
Thank you for your replies
> Not sure what you're asking about. The subject asks about "enabled" and then you talk about "exited"
Sorry the 'Active (enabled)' in the question was a mistake, I meant 'Active (exited)'.
> What problem do you have?
As mentioned the service does seem to be started, so there does not seem to be an immediate problem with the service itself.
I was, however, wondering:
a) exactly what it is which causes a service to have this status and why.
Most services when running indicate: 'active (running)'
(and also the legacy command 'service <servicename> status' successfully forwards to systemctl - in the case if nfs this does not work)
b) whether this matters, or is likely to be an issue.
c) if it is likely to be an issue how can I stop it from being so
> What do you mean by "recognise"?
I was referring to the statement "does not know there is a daemon to monitor." in the link I mentioned.
How do I get it to know there is a daemon to monitor ?
> Have you read the documentation?
I did read through this documentation, but I could not see any reference to 'active (exited)' status or how to tell it there is a daemon to monitor. I could well have missed, so will look again more thoroughly. There is also a link:
https://access.redhat.com/documentat...emd-unit_files
which may well be telling me the answer, but I'm not seeing it, so I'll try that again.