I see systemctl has this --user command for connecting to your user service manager. Is there a way to connect to somebody else's service manager? Like say I'm root and I want to put something in user $OTHERUSER's user service manager. I guess I just use sudo -u $OTHERUSER?
Well I was hoping that when you use it for its actual intended purpose (initing) systemd would turn out to be pleasant and usable as opposed to obscurantist and sharp-edged like it has been for every other purpose I've tried to use it for, but
$ sudo -u bsky systemctl --user daemon-reload
Failed to connect to bus: No such file or directory
journalctl has a --unit=UNIT command you can pass it that will cause it to journal for only one unit. The unit name here is defined by… what? The Description= in the .service file? The name of the .service file? The name of the .service file minus the suffix ".service"? A secret fourth thing?
Okay uhhhh I think I basically understand how to create and launch a systemd service now but I gotta say, despite it being a little less featureful I still think I like upstart better
@mcc SAME. And not just metaphorically because I'm the guy that tries the fringe features of stuff and starts loving them -- and is usually gutted when they get removed...
takes a deep breath
...but because RC is ACTUALLY A GREAT COLA and I don't care who knows I love it.
@mcc that...is a really good question. I think from a quick consult of systemd.unit(5) that the name is formally the filename including the suffix (.service or otherwise) with the big coming before being called the "name prefix" or "unit prefix" (these two terms appear to be synonyms and are used in adjacent sentences with no explanation)
But journalctl --unit also accepts a pattern, which is I think why journalctl --unit cybersyn will show you logs for cybersyn.service
@GBrayUT@SnoopJ Have you ever heard of Mercurial? It's a git alternative. Anyway there's a command in Mercurial that's incredibly useful, you find yourself typing it all the time, it's
Add comment