| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: [EXTERNAL] Re: Autostart with manage-procs and network mounts |
| From: | "Kasemir, Kay via Tech-talk" <tech-talk at aps.anl.gov> |
| To: | "Smith, William" <william.smith at helmholtz-berlin.de>, Michael Davidsaver <mdavidsaver at gmail.com> |
| Cc: | "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov> |
| Date: | Tue, 3 Aug 2021 17:22:46 +0000 |
|
> > 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 After=autofs.service Wants=autofs.service BindsTo=autofs.service -Kay
|