summaryrefslogtreecommitdiff
path: root/man
Commit message (Collapse)AuthorAgeFilesLines
* Merge pull request #24595 from ↵Daan De Meyer2022-10-101-0/+20
|\ | | | | | | | | rphibel/support-image-option-in-systemctl-and-coredumpctl systemctl/coredumpctl: add support for --root and --image options
| * coredumpctl: Add support for the --image optionRichard Phibel2022-10-031-0/+13
| |
| * coredumpctl: Add support for the --root optionRichard Phibel2022-10-031-0/+7
| | | | | | | | | | With this option, coredumpctl looks for journal files under the specified root directory
* | man: use a list for description of ConditionFirmware=Zbigniew Jędrzejewski-Szmek2022-10-091-27/+32
| | | | | | | | | | Also reduce confusion of <replaceable> and <literal> and reword things for legibility a bit.
* | Revert "journal: Add --convert= command to journalctl"Daan De Meyer2022-10-081-11/+0
| | | | | | | | | | | | This reverts commit 721620e8a32907ffe546a582c5ac7136b6367510. This commit was accidentally merged as part of #22998
* | man/shutdown: document how to switch to single-user modeanarcat2022-10-071-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before Debian switched to systemd, `shutdown now` would reset the system into single user mode, doing roughly the equivalent of `telinit 1`. Now, systemd's `shutdown` command does not behave that way; it defaults to `poweroff` which might be confusing for users (like me) used to the previous method. Because I don't use the command often, I keep being stumped by this behavior, and every time I look at the `shutdown(1)` manpage, I don't understand why I can't find what I am looking for. This patch should make sure that people like me find their way back to some sort of reason. Maybe the *proper* way to fix this would be to restore the more classic behavior, but I'm definitely not going to climb that hill. Besides, I clearly remember the time I found out about the `shutdown` command and was *really* confused when it brought me back to a command-line prompt. That was really counter-intuitive and I find that change to actually be a good thing. So I'm not proposing to change this behavior, merely document it better. I originally added this to the `-P` option but it was suggested adding a new `COMPATIBILITY` section instead, where other such issues could be added. The `COMPATIBILITY` section is not actually officially documented. `man(1)` talks about a `CONFORMING TO` section, but `shutdown(1)` is not POSIX (`shutdown(2)` is, of course), so there's no actual standard on how this should work. The other option I considered was to add a `BUGS` section, but that seemed to inflammatory, and definitely counter-productive.
* | Implement --luks-sector-size for homedAidan Dang2022-10-071-0/+1
| |
* | journal: Add --convert= command to journalctlDaan De Meyer2022-10-071-0/+11
| | | | | | | | | | | | | | | | --convert writes the journal files read by journalctl to the given location. The location should be specified as a full journal file path (e.g. /a/b/c/converted.journal). The directory specifies where the converted journal files will be stored. The filename specifies the naming convention the converted journal files will follow.
* | resolve: drop remaining references for Monitor=Yu Watanabe2022-10-031-9/+0
| | | | | | | | Follow-up for b25d819aee10b79a1c972d25be81a238448134dd.
* | resolve: fix typoYu Watanabe2022-10-031-1/+1
| |
* | Merge pull request #24878 from keszybz/condition-first-bootLuca Boccassi2022-10-014-22/+41
|\ \ | | | | | | Tweak condition first boot to use the same logic in pid1 and units
| * | man: add cross-links about preset operationsZbigniew Jędrzejewski-Szmek2022-10-013-9/+19
| | |
| * | manager: fix/change evaluation of ConditionFirstBootZbigniew Jędrzejewski-Szmek2022-10-012-14/+23
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The code to evaluate the kernel command line option was busted because it was doing 'return b == !!r' at a point where 'r > 0'. Thus we'd return "true" in both cases: $ SYSTEMD_PROC_CMDLINE=systemd.condition-first-boot build/systemd-analyze condition 'ConditionFirstBoot=true' test.service: ConditionFirstBoot=true succeeded. Conditions succeeded. $ SYSTEMD_PROC_CMDLINE=systemd.condition-first-boot build/systemd-analyze condition 'ConditionFirstBoot=false' test.service: ConditionFirstBoot=false succeeded. Conditions succeeded. We only use 'ConditionFirstBoot=true' in units, so this wasn't noticed. But I think the logic is broken in general: the condition should evaluate as true only during initial boot. If we rerun the units at later points, we should not consider ConditionFirstBoot to be true. Also, the first boot logic is also used in pid1 itself. AFAICT, for two things: in first boot machine-id is initialized transiently (this allows first-boot operations to be restarted if boot fails), and preset-all is executed. But this logic was different and separate from the logic to evaluate ConditionFirstBoot. The distinction is abolished, and the operations in pid1 now use the same logic as ConditionFirstBoot, which means that the kernel command line option is checked, and condition_test_first_boot() just tests whether pid1 thinks we're in first boot. This makes things easier to grok for the user: there's just one condition for "first boot" and it applies to both pid1 and units.
* | man: Update systemd.killMode docsClyde Byrd III2022-10-011-3/+10
| |
* | Merge pull request #24853 from poettering/resolved-monitor-fixesLuca Boccassi2022-09-305-26/+149
|\ \ | | | | | | resolved: various monitor fixes
| * | resolvectl: add new "monitor" verbLennart Poettering2022-09-301-1/+22
| | |
| * | resolved: don't make monitoring optionalLennart Poettering2022-09-301-5/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The socket is only accessible to privileged clients anyway, no need to add another (user unfriendly) restriction via opt-in setting. let's just allow this for privileged clients, mirroring "busctl monitor", or "tcpdump" and similar, which all just work if you have privs. (This does not break API, since we never did a release witht the "Monitor" dbus property or config setting in place, i.e. with cb456374e096f0ebe9b70d7ddd98e16a4be24ee6)
| * | sd-event: add helper for exiting event loop on SIGTERM/SIGINTLennart Poettering2022-09-302-0/+102
| | | | | | | | | | | | | | | | | | In many (most?) of our event loops we want to exit once SIGTERM/SIGINT is seen. Add a common helper for that, that does the right things in a single call.
| * | sd-event: if signal nr has high bit set sd_event_add_signal() auto-block it ↵Lennart Poettering2022-09-302-20/+25
| |/ | | | | | | | | | | | | | | | | via sigprocmask() So far we expected callers to block the signals manually. Which is usually a good idea, since they should do that before forking off threads and similar. But let's add a mode where we automatically block it for the caller, to simplify things.
* | portablectl: add --force attach/detachLuca Boccassi2022-09-302-1/+11
| | | | | | | | | | | | | | | | | | | | Allows to skip check that ensures units must not be running. I have a use case that would use reattach, except the orchestrator is using a non-standard versioning scheme, so image matching cannot work. As a workaround, need to be able to detach and then attach manually, without stopping the units to avoid extended downtimes and loss of FD store.
* | man: document the Dump() calls of the PID 1 D-Bus interface, and what they areLennart Poettering2022-09-301-4/+14
|/
* systemctl: add support for --image optionRichard Phibel2022-09-271-0/+13
| | | | | All tools that support --root= should also learn --image= so that they can operate on disk images directly.
* man: document that setting Storage= in namespaces journald menas ↵Lennart Poettering2022-09-261-0/+8
| | | | | | LogDirectory= in unit file needs setting too Replaces: #24789
* tree-wide: fix typoYu Watanabe2022-09-241-1/+1
|
* Merge pull request #24799 from poettering/initrd-ftwLuca Boccassi2022-09-2317-76/+64
|\ | | | | use "initrd" rather than "initial RAM disk" or "initramfs" to refernce the concept
| * tree-wide: also settle on "initrd" instead of "initial RAM disk"Lennart Poettering2022-09-239-34/+30
| | | | | | | | | | With this the concept is now called the same way everywhere except where historical info is relevant or where the other names are API.
| * tree-wide: use the term "initrd" at most places we so far used "initramfs"Lennart Poettering2022-09-239-42/+34
| | | | | | | | | | | | | | | | | | | | | | | | In most cases we refernced the concept as "initrd". Let's convert most remaining uses of "initramfs" to "initrd" too, to stay internally consistent. This leaves "initramfs" only where it's relevant to explain historical concepts or where "initramfs" is part of the API (i.e. in /run/initramfs). Follow-up for: b66a6e1a5838b874b789820c090dd6850cf10513
* | Merge pull request #24635 from DaanDeMeyer/repart-verity-sigDaan De Meyer2022-09-231-11/+15
|\ \ | | | | | | repart: Add support for generating verity sig partitions
| * | repart: Add support for generating verity sig partitionsDaan De Meyer2022-09-231-11/+15
| | |
* | | Merge pull request #24700 from poettering/ssh-credsLennart Poettering2022-09-233-21/+215
|\ \ \ | |_|/ |/| | support easy provisioning for SSH key of root user
| * | man: add man page decribing well known system credentialsLennart Poettering2022-09-232-0/+193
| | |
| * | man: document new : modified for uid/gid/access mode in tmpfiles.dLennart Poettering2022-09-231-21/+22
| |/
* | Merge pull request #24686 from d4nuu8/delta_outputLennart Poettering2022-09-231-0/+7
|\ \ | |/ |/| shared/logs-show: add new --output= format "short-delta"
| * shared/logs-show: add new --output= format "short-delta"Daniel Braunwarth2022-09-231-0/+7
| | | | | | | | | | | | | | This new output formatting option is similar to "short-monotonic" but also shows the time delta between two messages. This fixes #24641.
* | Merge pull request #24771 from poettering/destroy-pcr11Luca Boccassi2022-09-223-2/+166
|\ \ | | | | | | extend boot phase information into PCR 11 during boot
| * | measure: make --public-key= optional if "sign" is calledLennart Poettering2022-09-221-1/+4
| | | | | | | | | | | | | | | We can derive the public key from the private key, so let's do that, to make things a bit easier.
| * | measure: allow pre-calculating PCR values for multiple boot phasesLennart Poettering2022-09-221-0/+22
| | |
| * | boot: add new pcrphase tool to measure barrier strings into PCR 11Lennart Poettering2022-09-223-1/+140
| | |
* | | man/portablectl: fix references to optionsAntonio Alvarez Feijoo2022-09-221-2/+2
| | |
* | | repart: Add --split option to generate split artifactsDaan De Meyer2022-09-222-2/+66
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | For use with sysupdate or other systemd tooling, it's useful to be able to generate split artifacts from disk images, where each partition is written to a separate file. Let's support this with a --split switch for repart and a SplitName= configuration option. --split enables split artifacts generation, and SplitName= configures for which partition to generate split artifacts, and which suffix to add to the split artifact name. For SplitName=, we add support for some extra specifiers, more specifically the partition Type UUID and the partition UUID.
* | man: don't mention Socket files in Scope man pageJoost Heitbrink2022-09-221-1/+1
| |
* | Merge pull request #24709 from keszybz/partition-table-constantsLennart Poettering2022-09-2119-224/+176
|\ \ | | | | | | Expose various GPT UUIDs as public contants and link them up in docs
| * | man/systemd-gpt-auto-generator: reword phrasing about partition locationZbigniew Jędrzejewski-Szmek2022-09-201-12/+12
| | | | | | | | | | | | | | | | | | | | | | | | "located on the same disk as the ESP is located on" is hard to grok. Let's use more natural phrasing. Also, we shouldn't say that "The first foo partition … is mounted to …", because this doesn't explain what is happening. The partition could be empty, and there could be other partitions with the "foo" content, but what matters is the UUID.
| * | man/systemd-gpt-auto-generator: export type flags by name, trim tableZbigniew Jędrzejewski-Szmek2022-09-201-54/+21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We listed many of the root-partition type uuids, but not all. I think the chances of somebody using the discoverable partition magic on an Itanium system are fairly low at this point. So let's remove all architectures except the two most popular consumer architectures. People building Longsoon or RISC-V images are likely to have the online version of the Discoverable Partitions Specifications handy anyway, and it makes the man page easier to read. It also reduces the chances that somebody adding new entries to the table has some select&paste mishap. We've already had this happen in the past and it's fairly nasty bug. We don't need to expose the information in two places with manual propagation between them.
| * | headers: export partition uuids and flags in new sd-gpt.h fileZbigniew Jędrzejewski-Szmek2022-09-201-3/+3
| | | | | | | | | | | | | | | | | | I think those constants are generally useful. It's quite easy to make a mistake when copying things from the docs, so let's make them easy and convenient to access.
| * | man: "the initial RAM disk" → "the initrd"Zbigniew Jędrzejewski-Szmek2022-09-2018-158/+143
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In many places we spelled out the phrase behind "initrd" in full, but this isn't terribly useful. In fact, no "RAM disk" is used, so emphasizing this is just confusing to the reader. Let's just say "initrd" everywhere, people understand what this refers to, and that it's in fact an initramfs image. Also, s/i.e./e.g./ where appropriate. Also, don't say "in RAM", when in fact it's virtual memory, whose pages may or may not be loaded in page frames in RAM, and we have no control over this. Also, add <filename></filename> and other minor cleanups.
| * | man: add missing subject in sentenceZbigniew Jędrzejewski-Szmek2022-09-171-1/+1
| | |
* | | Merge pull request #24753 from DaanDeMeyer/repart-squashfsLennart Poettering2022-09-211-6/+6
|\ \ \ | | | | | | | | repart: Add squashfs support
| * | | repart: Add squashfs supportDaan De Meyer2022-09-211-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To make this work, we have to set up everything in a temporary directory tree that we can pass to mksquashfs as a single directory. To make the most common scenario more efficient, we skip the temporary setup directory if we only get a single source tree destined to root in the squashfs filesystem.
* | | | kernel-install.8: fix -h/-v ordering in SYNOPSISнаб2022-09-211-1/+1
| | | |
View Lorry Controller Status