systemd-run: update page

[metiulekm]

• The page(s) are in the correct platform directories: common, linux, osx, windows, sunos, android, etc.
• The page(s) have at most 8 examples.
• The page description(s) have links to documentation or a homepage.
• The page(s) follow the content guidelines.
• The PR title conforms to the recommended templates.
• Version of the command being documented (if known): systemd 253 (253-1-arch)

systemd-run is very versatile and it can basically do anything that can be done using the usual file-based configuration (with the obvious limitation of everything disappearing after a reboot), so I have documented the things I found the most useful personally.

[CLAassistant]

All committers have signed the CLA.

[kbdharun]

Welcome to tldr, Thanks for your contribution. I have some suggestions for this page.

[kbdharun]

Suggested change

	`systemd-run -u {{unit_name}} -- {{executable}} {{extra parameters ...}}`
	`systemd-run -u {{unit_name}} -- {{executable}} {{extra_parameters ...}}`

I am not 100% sure about this, would this be better?

[metiulekm]

I used the current version because CONTRIBUTING.md has {{path/to/directory1 path/to/directory2 ...}} as an example, and there can be multiple parameters. What do you think about this?

[EmilyGraceSeville7cf]

I am not 100% sure about this, would this be better?

According to yours style guide it's incorrect, ellipsis always contain two items, and not one before .... The original code was more right, but not completely. Solutions: {{arg1 arg2 ...}}, {{argument1 argument2 ...}}.

[blueskyson]

I prefer to {{argument1 argument2 ...}}.

[kbdharun]

I prefer to {{argument1 argument2 ...}}.

Yeah, seems better

[metiulekm]

Thank you so much! 😸

[metiulekm]

I used the current version because CONTRIBUTING.md has {{path/to/directory1 path/to/directory2 ...}} as an example, and there can be multiple parameters. What do you think about this?

[blueskyson]

I prefer to {{argument1 argument2 ...}}.

[metiulekm]

Thanks a lot @EmilySeville7cfg and @blueskyson!

[EmilyGraceSeville7cf]

@EmilySeville7cfg, I have no idea what that means stuck_out_tongue So, what should I do?

Style guide contains this phrase:

For any reference to paths of files or directories, use the format {{path/to/}}, except when the location is implicit.

My original suggestion was to change placeholder to {{path/to/executable}}/{{path/to/executable_file}}. But on the other hand, there is such note: when the location is implicit (to avoid confusion it should be strictly defined). It's not clear what is implicit here. If it means that location is determined from $PATH, then you can leave placeholder as it is.

P.S. Here is another issue with it: what if location can be both implicit (like I defined this term) and explicit? It's undefined what to write here. Possible solution: change sentence to:

For any reference to paths of files or directories, use the format {{path/to/}}, except when the location can be implicit.

But then we lose an ability to present just implicit paths. Besides, completely another way can be chosen: don't care about implicit locations at all and assume that any path/to/* placeholder can represent implicit location.

[metiulekm]

P.S. Here is another issue with it: what if location can be both implicit (like I defined this term) and explicit? It's undefined what to write here.

If I understand correctly what you mean, this is exactly the case, as both let's say systemd-run whoami and systemd-run /usr/bin/whoami will work. The same is also true for the other tools I mentioned (gdb and which).

So in the end, what should I do? @kbdharun and @blueskyson 👍'd keeping {{executable}} as is, but I am in no way opposed to changing it to {{path/to/executable}}.

[github-actions]

Hi all! This thread has not had any recent activity.
Are there any updates? Thanks!

[github-actions]

Hi everyone.
This thread is being closed as there was no response to the previous prompt.
However, please leave a comment whenever you're ready to resume, so the thread can be reopened.
Thanks again!