On 27/03/2021 07:20, Patrick O'Callaghan wrote:
This never happens if I run the script directly from the command line
(i.e. the drives power down and stay down).
Clearly the docking unit isn't just doing this flakily on its own.
Something is making it happen, and I've no idea how to discover what it
is except that it seems to be correlated with systemd in some way.
Just "thinking out loud" here.
When you run the script from the command line it is after you've determined the
unmount
has happened. How much time do you think elapsed between the actual unmount and
running of the script? Do you have a delay between the time inotifywait
detects unmount
and powering down the drives? If so, does it help if you extend the delay?
I have never used it for this, but wireshark does have the ability to monitor
USB. Don't
know if that will reveal anything or be of any help.
--
Remind me to ignore comments which aren't germane to the thread.
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
