On Mon, 2021-03-15 at 10:40 +0800, Ed Greshko wrote: > On 15/03/2021 07:37, Patrick O'Callaghan wrote: > > The only remaining problem (touch wood) is to get the power-down > > script > > to run after a timeout. I'll consider writing a special script to > > monitor the mount status independently of systemd. > > You can consider using the timer/service pair of systemd. > > Add another Wants to raid.mount of say "raid.timer". Then.... > > 1. Upon mount, raid.timer is started. > 2. After defined time, raid.timer calls "raid.service". > 3. raid.service checks mount status. > 4. If still mounted then exit. Meaning goes back to waiting and #2. > 5. If now unmounted, power off the hub and stop raid.timer. So, > basically, raid.service no long runs > and you're back to condition #1 which starts the timer again on > the next mount. OK, I'm attempting to do that, but it's not quite there. The main problem seems to be getting the timer to fire more than once (did I mention how obscure the systemd docs are?). As it stands, the raid.service unit checks the mounted status immediately rather than waiting, and of course it always succeeds, but then just finishes. I attach the current systemd files. The 'dock' script is now considerably simplified (it turns out that all the bus scanning is unnecessary as I can just use ' hdparm -y' to spin down, and spinning up is automatic). The 'cdown' argument powers down the dock conditionally, i.e. if it's not mounted. poc
Attachment:
raid.tar
Description: Unix tar archive
_______________________________________________ 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
