On 13/03/2021 01:29, Patrick O'Callaghan wrote:
On Fri, 2021-03-12 at 22:39 +0800, Ed Greshko wrote:
Does something need running when the share goes from unmounted to
mounted?
Just a timer. Once it's powered up and mounted, it should stay that
way
until an idle timeout is triggered.
That statement confuses me. Isn't that what happens with automount
and the TimeoutIdleSec=
parameter?
<snip>
Of course it's possible that sending some command to the dock would
power down the drives, but the thing has no useful documentation. It
just comes with (of course) a Windows driver.
OK.... My understanding is that the HW you have doesn't power-down or power-up (wake-up) in
response to an unmount or mount operation.
So, in the case of automount/autounmount you need "something" to
issue power-up command followed by mount
and
unmount followed by issue power-down command
So, it does sound to me your configuration is very "non-standard" and not common.
It also sounds like you're trying to workaround deficiencies in HW that seems to have
been designed with Windows in mind.
I don't think systemd was meant to solve these sorts of issues And a kludge is more
fitting than trying to shoehorn in a standard tool. Of course you then, potentially,
have to maintain the kludge. I used to do that. But no longer. I found other "hobbies". :-)
--
People who believe they don't make mistakes have already made one.
_______________________________________________
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
