Replies: 2 comments 2 replies
-
Perhaps, |
Beta Was this translation helpful? Give feedback.
1 reply
-
I mean, if you want a specific step to happen after that service runs, then make it happen before that service, not the broader target. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a Debian 12 system with several ZFS datasets. Some are encryption roots with passphrases. Entering the passphrases on reboot is obviously inconvenient so I'd like to switch this up to pull from a secrets manager (in this case 1Password, but I don't think that's necessarily relevant) with a service account and store the keys in a
tmpfs
so they aren't persisted on disk.I have my 1Password
systemd
service unit that pulls the passphrase down into a file working great. But I'm having trouble with the ordering of it.I thought this would be as simple as
1password.service
:but things don't always run in the right order so after a reboot I find myself on a box where the key files are present in
tmpfs
butzfs get keystatus
showsunavailable
because the[email protected]
has failed saying the file doesn't exist.Has anyone done something similar and got any tips for reliably ordering something to start up and execute before OpenZFS tries importing the pool/datasets? Thanks!
Beta Was this translation helpful? Give feedback.
All reactions