CAUTION: *** EMAIL ORIGINATED FROM OUTSIDE THE ORGANIZATION. Please do not click links or open attachments unless you know the contents are safe. Verify that you recognize sender email address before clicking any link or attachment. DO NOT enter/change any password when clicking on a link. ***
On 8/3/21 10:22 AM, Kasemir, Kay wrote:
I am using manage-procs to deploy and manage IOC’s using systemd. ..network drive over nfs at boot that contains the built IOC binaries
I think that "After=network.target remote-fs.target" should be enough to ensure ordering. You could try adding
"Requires=network.target remote-fs.target".
I think we had similar issues with network mounts not being up in time for the IOCs to start when we had just this in the IOC systemd files:
Requires=autofs.service
The following belt-and-suspenders approach fixed the problem, though I'm not sure exactly why:
Requires=autofs.service
I would be reluctant to blindly add this as I think it would make manage-procs
unusable by default for installations w/o autofs. If a Requires= turns out to
be necessary, manage-procs would probably have to detect this somehow.
This is actually redundant to "BindsTo=autofs.service".
After=autofs.service
This seems reasonable, and would hopefully be sufficient by itself.
Wants=autofs.service
This should probably be ok, but would need some testing. I would expect that
if autofs is installed, that it is installed and should be running.
BindsTo=autofs.service
cf. https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.freedesktop.org%2Fsoftware%2Fsystemd%2Fman%2Fsystemd.unit.html%23Wants%3D&data=04%7C01%7Cernesto_paiser%40lynceantech.com%7C8957d5d1168e456191d808d956a4fcb7%7C49fa64a600cf42d48c52cc94b9a02f26%7C1%7C0%7C637636088892767139%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=FPXFNVRz%2FIbW76Z2C5V37QY243PGEny2ILT4Ws%2FaBcs%3D&reserved=0
