summaryrefslogtreecommitdiffstats
path: root/catalog (follow)
Commit message (Collapse)AuthorAgeFilesLines
* catalog: update Polish translationPiotr Drąg2023-07-141-0/+22
|
* 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.
* catalog,po: update Polish translationPiotr Drąg2023-06-271-1/+38
|
* 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.
* meson: Install all catalogsJan Janssen2023-01-271-2/+8
|
* 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-312-7/+7
| | | | | | | Original catalog file is in English Move the repeating German message to German catalog Signed-off-by: Alexander Shopov <ash@kambanaria.org>
* Update Bulgarian translationAlexander Shopov2022-05-311-53/+273
| | | | | | po: catalog: Bring bg.po and catalog file to 100% Signed-off-by: Alexander Shopov <ash@kambanaria.org>
* catalog,po: update Polish translationPiotr Drąg2022-05-151-0/+18
|
* 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.
* meson: do not use split() in file listsZbigniew Jędrzejewski-Szmek2022-03-021-14/+13
| | | | | | | | | | | The approach to use '''…'''.split() instead of a list of strings was initially used when converting from automake because it allowed identical blocks of lines to be used for both, making the conversion easier. But over the years we have been using normal lists more and more, especially when there were just a few filenames listed. This converts the rest. No functional change.
* meson: Add missing test dependenciesDaan De Meyer2022-01-211-1/+1
| | | | | | Currently, running "meson build" followed by "meson test -C build" will result in many failed tests due to missing dependencies. This commit adds the missing dependencies to make sure no tests fail.
* units: added factory-reset.targetYegor Alexeyev2021-08-101-0/+9
|
* meson: revert the change to unquote commands in add_install_scriptZbigniew Jędrzejewski-Szmek2021-05-141-1/+1
| | | | | | | | | Old meson fails with: Element not a string: [<Holder: <ExternalProgram 'sh' -> ['/bin/sh']>>, '-c', 'test -n "$DESTDIR" || /bin/journalctl --update-catalog'] I'm doing it as a revert so that it's easy to undo the revert when we require newer meson. The effect is not so bad, maybe a dozen or so lines about finding 'sh'.
* meson: call find_program() once and reuse the variable everywhereZbigniew Jędrzejewski-Szmek2021-05-141-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Meson 0.58 has gotten quite bad with emitting a message every time a quoted command is used: Program /home/zbyszek/src/systemd-work/tools/meson-make-symlink.sh found: YES (/home/zbyszek/src/systemd-work/tools/meson-make-symlink.sh) Program sh found: YES (/usr/bin/sh) Program sh found: YES (/usr/bin/sh) Program sh found: YES (/usr/bin/sh) Program sh found: YES (/usr/bin/sh) Program sh found: YES (/usr/bin/sh) Program sh found: YES (/usr/bin/sh) Program xsltproc found: YES (/usr/bin/xsltproc) Configuring custom-entities.ent using configuration Message: Skipping bootctl.1 because ENABLE_EFI is false Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Message: Skipping journal-remote.conf.5 because HAVE_MICROHTTPD is false Message: Skipping journal-upload.conf.5 because HAVE_MICROHTTPD is false Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Message: Skipping loader.conf.5 because ENABLE_EFI is false Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) Program ln found: YES (/usr/bin/ln) ... Let's suffer one message only for each command. Hopefully we can silence even this when https://github.com/mesonbuild/meson/issues/8642 is resolved.
* license: LGPL-2.1+ -> LGPL-2.1-or-laterYu Watanabe2020-11-0918-18/+18
|
* tree-wide: update web link to logind descriptionZbigniew Jędrzejewski-Szmek2020-10-1916-64/+64
| | | | | 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.
* catalog: add missing @ to German catalog fileLennart Poettering2020-09-231-1/+1
|
* catalog: update Polish translationPiotr Drąg2020-07-261-0/+36
|
* 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.
* catalog: update Polish translationPiotr Drąg2020-07-051-3/+57
|
* 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,po: update Polish translationPiotr Drąg2020-05-041-0/+23
|
* catalog: add entry for SD_MESSAGE_UNSAFE_USER_NAMELennart Poettering2020-04-081-0/+23
|
* Update Croatian translation (#15042)gogogogi2020-03-081-4/+4
|
* catalog: update Polish translationPiotr Drąg2019-07-291-0/+9
|
* catalog: reference ExecCondition= in unit skipped strAnita Zhang2019-07-181-1/+2
|
* core: ExecCondition= for servicesAnita Zhang2019-07-171-0/+7
| | | | Closes #10596
* po: minor fixes to Italian translation (#12500)Daniele Medri2019-05-091-17/+17
|
* Systemd Catalog, Italian translation: minor updates (#12483)Daniele Medri2019-05-061-19/+129
|
* codespell: fix spelling errorsBen Boeckel2019-04-291-1/+1
|
* catalog: update Polish translationPiotr Drąg2019-04-231-0/+14
|
* catalog: add a new catalog entry explaining the new OOM killer event log msgLennart Poettering2019-04-091-0/+13
|
* catalog: update Polish translationPiotr Drąg2018-11-191-20/+52
|
* 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).
* Drop copyright for Piotr DrągZbigniew Jędrzejewski-Szmek2018-10-311-2/+0
| | | | | | Ack in #9320. Also drop some lines with my name.
* catalog: update Polish translationPiotr Drąg2018-10-301-2/+4
|
* 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-1616-48/+48
| | | | | | | | | | 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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-11 16:49:59 +0100