On Thu, 2021-03-11 at 13:13 +0000, Patrick O'Callaghan wrote: > On Thu, 2021-03-11 at 07:47 -0500, Jonathan Billings wrote: > > On Mar 10, 2021, at 20:18, Ed Greshko <ed.greshko@xxxxxxxxxxx> wrote: > > > > > > The answer may be "none of the above". > > > > > > Diving into systemd documentation it seems that the sections included in the mount and automount unit files > > > don't define those lines. :-( > > > > There isn’t anything about exec lines in a .mount unit, which is why I said to have a .service unit that is a requirement and is triggered to start / stop when the mount is mounted / unmounted. > > > > Here’s my post: > > https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx/message/ZQALAORVT7A5KPERZUX7U2CLEXJ2PBLC/ > > Yes, I had noticed that. What isn't clear to me is how this would work > on system reboot. I need to be able to power down the drive not just > after it's unmounted, but when the system is rebooted and the drive > hasn't been mounted in the first place, i.e. a non-event. Someone on the SystemD list suggested using an @reboot line in crontab for this, as a special case. poc _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
