summaryrefslogtreecommitdiffstats
path: root/catalog/systemd.catalog.in (follow)
Commit message (Collapse)AuthorAgeFilesLines
* portable: log structured message when attach/detach succeedsLuca Boccassi2024-01-191-0/+20
| | | | | | | | | | | | | | Currently portabled is completely silent (when not using debug level). But when the system state is changed (ie: a portable is attached or detached) there are no traces left in the journal. Log at info level when either of those operations succeed, as they are effectively changing the state of the system. Create new MESSAGE_IDs for these logs, and also append PORTABLE_ROOT= (and PORTABLE_EXTENSION= if any), like the units themselves are configured to do via LogExtraFields=, so that the same metadata can be found in the attach/detach messages and in logs from the units themselves.
* tree-wide: s/life-cycle/lifecycle/gZbigniew Jędrzejewski-Szmek2023-11-061-1/+1
|
* tree-wide: fix typoYu Watanabe2023-10-311-1/+1
|
* systemd.catalog: freezed -> frozeMike Yuan2023-09-051-2/+2
| | | | Follow-up for 1dc604d821b6f9519e1961b154ae37baad57dbb1
* catalog/systemd.catalog: rephrase a bunch of messagesMike Yuan2023-09-041-36/+43
| | | | Follow-up for #28873
* Journal: Add message IDs for emergency-level log messagesOMOJOLA JOSHUA2023-09-011-0/+159
|
* Drop split-usr and unmerged-usr supportLuca Boccassi2023-07-281-2/+0
| | | | | | | | | | As previously announced, execute order 66: https://lists.freedesktop.org/archives/systemd-devel/2022-September/048352.html The meson options split-usr, rootlibdir and rootprefix become no-ops that print a warning if they are set to anything other than the default values. We can remove them in a future release.
* sysv-generator: make sysv deprecation message a bit "louder"Lennart Poettering2023-06-271-0/+20
| | | | | | | Let's add a catalog entry, make the log record structured, and most importantly, let's add warning emojis. Just to underline that this stuff should really go away.
* tree-wide: when in doubt use greek small letter mu rather than micro symbolLennart Poettering2023-06-141-1/+1
| | | | | | | | Doesn't really matter since the two unicode symbols are supposedly equivalent, but let's better follow the unicode recommendations to prefer greek small letter mu, as per: https://www.unicode.org/reports/tr25
* man,catalog: fix typoYu Watanabe2023-02-241-1/+1
| | | | Follow-up for #26448.
* sd-event: add high-level sd_event_add_memory_pressure() event sourceLennart Poettering2023-02-221-0/+15
| | | | | | | | | | | | | | | | | | | | | | | | Typically, in reasonably complex programs we want to realease various caches (such as glibc allocation caches) in case of memory pressure. Let's add explicit infrastructure for that to sd-event, that can hook Linux' Pressure Stall Information (PSI) logic with our event loop. This adds sd_event_add_memory_pressure() as easy, one-step API to install an even source that is called under memory pressure. The parameters which file to watch (the per-cgroup PSI file, or the system-wide file /proc/pressure/memory) can be configured via env vars. The idea is that the service manager sooner or later gains controls for setting this up correctly. Alternatively to the PSI a similar logic is supported but instead of waiting for POLLPRI on a procfs/cgroupfs fd we'll wait for POLLIN on FIFO or AF_UNIX sockets. This is useful for testing, and possibly in other environments, for example to hook up this protocol directly with GNOME's low memory monitor. By default this watches on the cgroup-local PSI so that we aren't affected by pressure on cgroups we are not related to.
* timesyncd: write structured log messages whenever we bump the clock based on ↵Lennart Poettering2023-01-201-0/+9
| | | | | | | | | | | | disk timestamp It's useful being able to easily detect if a disk-based clock bump was done, let's make it a structure message, the same way as acquiring an NTP fix already is. Also, set the clock to 1 µs further than the timestamp from the disk, after all we know that that timestamp was current when it was written, hence it can't be the right one right now anymore.
* man: reword "string is extended into PCR"Zbigniew Jędrzejewski-Szmek2023-01-111-5/+6
| | | | | | | | | | | | | Originally, people used "extend a PCR with a measurement" or "measure some blob into the PCR". In our docs those uses got merged into "extend a string into a PCR". The meaning is clear to developers, but it's a very jargony syntax that wouldn't make any sense to somebody who encounters it the first time. Let's return to the more natural original phrasing. Also, change various "this is supposed to act as" to "this acts as". If it doesn't work, we have a bug to fix. This indirection is not useful. Also, "boot path" → "phase path" and other smaller cleanups.
* man: reword some awkward sentencesZbigniew Jędrzejewski-Szmek2022-10-141-1/+1
|
* tree-wide: also settle on "initrd" instead of "initial RAM disk"Lennart Poettering2022-09-231-1/+1
| | | | | With this the concept is now called the same way everywhere except where historical info is relevant or where the other names are API.
* boot: add new pcrphase tool to measure barrier strings into PCR 11Lennart Poettering2022-09-221-0/+12
|
* Move message repeatAlexander Shopov2022-05-311-7/+0
| | | | | | | Original catalog file is in English Move the repeating German message to German catalog Signed-off-by: Alexander Shopov <ash@kambanaria.org>
* timesyncd: generate a structure log message the first time we set the clock ↵Lennart Poettering2022-03-181-0/+8
| | | | | | | | | | correctly Usecase: later on we can use this to retroactively adjust log output in journalctl or similar on systems lacking an RTC: we just have to search for this sructured log message that indicates the first sync point and can then retroactively adjust the incorrect timestamps collected before that.
* units: added factory-reset.targetYegor Alexeyev2021-08-101-0/+9
|
* license: LGPL-2.1+ -> LGPL-2.1-or-laterYu Watanabe2020-11-091-1/+1
|
* tree-wide: update web link to logind descriptionZbigniew Jędrzejewski-Szmek2020-10-191-4/+4
| | | | | https://www.freedesktop.org/wiki/Software/systemd/multiseat/ says that it is obsoleted by sd-login(3), so it doesn't make much sense to link to the former.
* udevadm: beef up deprecation log warningLennart Poettering2020-07-141-0/+33
| | | | | | | | Let's add a catalog entry explaining further details. Most importantly though: talk to PID 1 directly, via the private D-Bus socket, so that this actually works correctly during early boot, where D-Bus is not around.
* pid1: warn if people use User=nobody (#16293)Lennart Poettering2020-06-261-0/+20
|
* catalog: normalize how we link to documentationLennart Poettering2020-05-291-5/+3
|
* core: improve log messages when we cannot process a mount pointLennart Poettering2020-05-261-0/+31
| | | | | | | | | | | | Whenever we pick up a new line in /proc/self/mountinfo and want to synthesize a new mount unit from it, let's say which one it is. Moreover, downgrade the log message when we encounter a mount point with an overly long name to LOG_WARNING, since it's generally fine to ignore such mount points. Also, attach a catalog entry to explain the situation further. Prompted-By: #15221
* catalog: add entry for SD_MESSAGE_UNSAFE_USER_NAMELennart Poettering2020-04-081-0/+23
|
* catalog: reference ExecCondition= in unit skipped strAnita Zhang2019-07-181-1/+2
|
* core: ExecCondition= for servicesAnita Zhang2019-07-171-0/+7
| | | | Closes #10596
* codespell: fix spelling errorsBen Boeckel2019-04-291-1/+1
|
* catalog: add a new catalog entry explaining the new OOM killer event log msgLennart Poettering2019-04-091-0/+13
|
* core: log a recognizable message when a unit succeeds, tooLennart Poettering2018-11-161-0/+7
| | | | | | We already are doing it on failure, let's do it on success, too. Fixes: #10265
* core: make log messages about unit processes exiting recognizableLennart Poettering2018-11-161-0/+9
|
* core: make log messages about units entering a 'failed' state recognizableLennart Poettering2018-11-161-0/+7
| | | | | Let's make this recognizable, and carry result information in a structure fashion.
* catalog: update job begin/done messagesLennart Poettering2018-11-161-20/+28
| | | | | | | | | | | | | | These texts have been slightly misleading previously, as they talked about units, not jobs, but are actually generated for jobs, not units. This difference matters as units can change state without a job requesting that. Also, the message be02cf6855d2428ba40df7e9d022f03d was particularly wrong, as it claimed the unit failed, while it actually is the start job that failed, which is a major difference, as jobs can fail without the unit actually being placed in a failed state. Let's move this message a bit up, closed to 39f53479d3a045ac8e11786248231fbf (i.e. the message seen when a start job finished successfully).
* core: implement per unit journal rate limitingAnita Zhang2018-10-181-1/+2
| | | | | | | | | Add LogRateLimitIntervalSec= and LogRateLimitBurst= options for services. If provided, these values get passed to the journald client context, and those values are used in the rate limiting function in the journal over the the journald.conf values. Part of #10230
* catalog: fix name of variableZbigniew Jędrzejewski-Szmek2018-10-161-3/+3
| | | | | | | | | | All the messages would (literally) say "The start-up result is RESULT." because @RESULT@ was not defined. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1639482 and the first part of #8005. Fixup for 646cc98dc81c4d0edbc1b57e7bca0f474b47e270.
* tree-wide: remove Lennart's copyright linesLennart Poettering2018-06-141-2/+0
| | | | | | | | | | | These lines are generally out-of-date, incomplete and unnecessary. With SPDX and git repository much more accurate and fine grained information about licensing and authorship is available, hence let's drop the per-file copyright notice. Of course, removing copyright lines of others is problematic, hence this commit only removes my own lines and leaves all others untouched. It might be nicer if sooner or later those could go away too, making git the only and accurate source of authorship information.
* tree-wide: drop 'This file is part of systemd' blurbLennart Poettering2018-06-141-2/+0
| | | | | | | | | | | | | | | | This part of the copyright blurb stems from the GPL use recommendations: https://www.gnu.org/licenses/gpl-howto.en.html The concept appears to originate in times where version control was per file, instead of per tree, and was a way to glue the files together. Ultimately, we nowadays don't live in that world anymore, and this information is entirely useless anyway, as people are very welcome to copy these files into any projects they like, and they shouldn't have to change bits that are part of our copyright header for that. hence, let's just get rid of this old cruft, and shorten our codebase a bit.
* tree-wide: drop license boilerplateZbigniew Jędrzejewski-Szmek2018-04-061-13/+0
| | | | | | | | | | Files which are installed as-is (any .service and other unit files, .conf files, .policy files, etc), are left as is. My assumption is that SPDX identifiers are not yet that well known, so it's better to retain the extended header to avoid any doubt. I also kept any copyright lines. We can probably remove them, but it'd nice to obtain explicit acks from all involved authors before doing that.
* Make taint message structured and add catalog entryZbigniew Jędrzejewski-Szmek2017-12-141-0/+17
| | | | | | | | | | | | | | | | | | | Dec 14 14:10:54 krowka systemd[1]: System is tainted: overflowgid-not-65534 -- Subject: The system is configured in a way that might cause problems -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The following "tags" are possible: -- - "split-usr" — /usr is a separate file system and was not mounted when systemd -- was booted -- - "cgroups-missing" — the kernel was compiled without cgroup support or access -- to expected interface files is resticted -- - "var-run-bad" — /var/run is not a symlink to /run -- - "overflowuid-not-65534" — the kernel user ID used for "unknown" users (with -- NFS or user namespaces) is not 65534 -- - "overflowgid-not-65534" — the kernel group ID used for "unknown" users (with -- NFS or user namespaces) is not 65534 -- Current system is tagged as overflowgid-not-65534.
* catalog: don't say "systemd" when we mean "system"Lennart Poettering2017-12-131-1/+1
| | | | | Yeah, it's hard to type "system", if all you ever type is "systemd", but it's still a typo in this case.
* Add SPDX license identifiers to catalog and po filesZbigniew Jędrzejewski-Szmek2017-11-191-0/+2
|
* catalog: split out the one German language entry we have in systemd.catalog ↵Lennart Poettering2017-09-261-12/+0
| | | | | | | into its own file All other languages have their own file, let's make sure German does too.
* catalog: add two recent message ID additions to catalogLennart Poettering2017-09-261-0/+15
| | | | | | | | Just brief texts for now, so that we have something (And in the long rung we should beef all this up, and add a test that every ID listed in sd-messages.h is accompanied by a matching catalog entry)
* catalog: use https:// in URLsAsciiWolf2017-02-211-5/+5
|
* pid1,catalog: use a different MESSAGE_ID for user manager startupZbigniew Jędrzejewski-Szmek2016-12-111-2/+13
| | | | | | | | | | | | This add a new message id for the end of user instance startup. User manager startup is a different beast then the system startup. Their descriptions are completely different too. Let's just separate them. Partially fixes #3351. Also remove "successful" from the description, since we don't know if the startup was successful or not.
* coredump,catalog: give better notice when a core file is truncatedZbigniew Jędrzejewski-Szmek2016-09-281-0/+11
| | | | | | | | | | | | | | | coredump had code to check if copy_bytes() hit the max_bytes limit, and refuse further processing in that case. But in 84ee0960443, the return convention for copy_bytes() was changed from -EFBIG to 1 for the case when the limit is hit, so the condition check in coredump couldn't ever trigger. But it seems that *do* want to process such truncated cores [1]. So change the code to detect truncation properly, but instead of returning an error, give a nice log entry. [1] https://github.com/systemd/systemd/issues/3883#issuecomment-239106337 Should fix (or at least alleviate) #3883.
* catalog: make support URL to show in shipped catalog entries configurable ↵Lennart Poettering2016-06-261-0/+334
(#3597) Let's allow distros to change the support URL to expose in catalog entries by default. It doesn't make sense to direct end-users to the upstream project for common errors. This adds a --with-support-url= switch to configure, which allows overriding the default at build-time. Fixes: #2516
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-29 23:36:01 +0100