What's the advantage to

  systemctl --host foo status httpd.service

  ssh -t foo systemctl status httpd.service

?

> What's the advantage to ...

For me personally, I'd say "not much". I'm used to using the latter form, and it's fine. But I will say that now that I know about this, I see using it in scenarios where I'm running a lot of systemctl commands over and over again in close proximity and have the "muscle memory" of typing "systemctl" more in mind.

For example, when working with a new service that isn't quite working right yet, and doing many iterations of:

    $> systemctl start something.service
    $> systemctl status something.service
    $> journalctl -xeu something.service
    $> emacs whatever
    $> systemctl start something.service
    $> systemctl status something.service
    lather, rinse, repeat

To be fair though, it's all a pretty minor point. But I do think it's cool that systemctl has that option. shrug

Was wondering the same. "Do one thing and do it well" philosophy...

If I want to run remote commands, I know how to do that already (namely, as you've shown), why learn to use a new tool for it? It's like these options to tar for compression: if I want to have a gzipped tar I'll run the tar c /sdcard output through |gzip thank you very much! (and drop in zstd instead)