You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wanted to programmatically restart a systemd service, and since I didn't want to set the SYSTEMCTL_PATH variable, I used https://github.com/lucab/zbus_systemd instead. The advantage to using the zbus crate is that it is less hacky / unstable because it uses D-Bus instead of the CLI. Can zbus_systemd replace all uses of this crate? Are there some scenarios where this crate is still the better choice?
Even if zbus_systemd can't replace this crate entirely, it would still be good to mention in the README that zbus_systemd might be the better way of controlling systemd with Rust.
After I made this issue I realized that #2 already exists, but nothing was really done with that issue, so I think replacing this crate / mentioning the zbus crate in the README should be reconsidered.
The text was updated successfully, but these errors were encountered:
I wanted to programmatically restart a systemd service, and since I didn't want to set the
SYSTEMCTL_PATH
variable, I used https://github.com/lucab/zbus_systemd instead. The advantage to using the zbus crate is that it is less hacky / unstable because it uses D-Bus instead of the CLI. Canzbus_systemd
replace all uses of this crate? Are there some scenarios where this crate is still the better choice?Even if
zbus_systemd
can't replace this crate entirely, it would still be good to mention in the README thatzbus_systemd
might be the better way of controlling systemd with Rust.After I made this issue I realized that #2 already exists, but nothing was really done with that issue, so I think replacing this crate / mentioning the zbus crate in the README should be reconsidered.
The text was updated successfully, but these errors were encountered: