summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Revert "resolvectl: Add show-multicast verb to show discovered LLMNR/mDNS hosts"revert-18355-resolved-discoverLennart Poettering2021-02-048-246/+14
|
* man: reword the description of "main conf file"Zbigniew Jędrzejewski-Szmek2021-02-041-24/+21
| | | | | | While not really "wrong", the text we had could use a little editing. Fixes #18458.
* Merge pull request #18444 from anitazha/proprenameZbigniew Jędrzejewski-Szmek2021-02-0427-143/+260
|\ | | | | oom: parse properties with 1/10000 precision instead of 1/100
| * oom: rework *MemoryPressureLimit= properties to have 1/10000 precisionAnita Zhang2021-02-0224-104/+91
| | | | | | | | | | | | | | Requested in https://github.com/systemd/systemd/pull/15206#discussion_r505506657, preserve the full granularity for memory pressure limits (permyriad) instead of capping out at percent.
| * parse-util: add permyriad parsingAnita Zhang2021-02-023-39/+169
| |
* | Merge pull request #18355 from DaanDeMeyer/resolved-discoverZbigniew Jędrzejewski-Szmek2021-02-048-14/+246
|\ \ | | | | | | resolvectl: Add show-multicast verb to show discovered LLMNR/mDNS hosts
| * | resolve: Add show-multicast verbDaan De Meyer2021-01-312-1/+95
| | | | | | | | | | | | | | | The show-multicast verb calls the GetMulticastHosts() D-Bus method and displays all its results formatted into a table.
| * | resolve: Add GetMulticastHosts() D-Bus methodDaan De Meyer2021-01-305-13/+146
| | | | | | | | | | | | | | | | | | GetMulticastHosts() returns an array of hostnames/addresses discovered via LLMNR or Multicast DNS. It does not trigger any discovery on its own. Instead, it simply returns whatever is already in resolved's cache.
| * | mkosi: Add a postinstall script to setup .gdbinit.Daan De Meyer2021-01-301-0/+5
| | | | | | | | | | | | | | | | | | | | | systemd is compiled with relative source file paths so we need to issue a directory command to make sure gdb can find systemd's source files. Let's put this in a .gdbinit file so it's executed automatically when we run gdb.
* | | Merge pull request #18462 from poettering/copy-timeYu Watanabe2021-02-041-17/+10
|\ \ \ | | | | | | | | timestamp fixes in copy.c
| * | | copy: simplify futimens() invocationLennart Poettering2021-02-031-15/+3
| | | |
| * | | copy: also attempt to copy atime/mtime when copying symlinks, device nodes, ↵Lennart Poettering2021-02-031-2/+7
| | | | | | | | | | | | | | | | fifos
* | | | import: use +i (immutable) chattr flag for marking OS images read-onlyLennart Poettering2021-02-041-14/+25
| | | | | | | | | | | | | | | | | | | | This is what nspawn and machine-image.[ch] actually look for, hence us it here too.
* | | | import: fix etag detection supportLennart Poettering2021-02-041-16/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let's make sure we still look at the etags reported by http 304 (i.e. the cache management code). Otherwise we won't properly realize we already downloaded this before. This fixes a bug introduced in 6792cbbcf84b730f465decbeaf247c6b1ccf1c18
* | | | Merge pull request #18459 from poettering/discover-imageYu Watanabe2021-02-0420-25/+27
|\ \ \ \ | | | | | | | | | | shared: rename machine-image.[ch] → discover-image.[ch]
| * | | | discover-image: don't mix two types of stack allocation in one lineLennart Poettering2021-02-031-5/+7
| | | | |
| * | | | shared: rename machine-image.[ch] → discover-image.[ch]Lennart Poettering2021-02-0320-20/+20
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The old name originates when this was used to discover "machine" images, as managed by machined/machinectl. But nowadays this is also used by portable services and system extensions, hence let's use a more generic name for this API. Taking inspiration from "dissect-image.[ch]", let's call this "discover-image.[ch]". This is pure renaming, no other changes.
* | | | path-util: tighten path_is_valid() checksLennart Poettering2021-02-032-9/+55
|/ / / | | | | | | | | | | | | This tightens the path_is_valid() checking: it now tests whether each component in the path is bound by FILENAME_MAX in its size.
* | | test-network: disable NDISC on veth-peerYu Watanabe2021-02-031-0/+1
| | | | | | | | | | | | This should speed the tests up.
* | | Deprecate builds with split-usr, prepare for removalZbigniew Jędrzejewski-Szmek2021-02-032-3/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There is no technical reason to support systems with split-usr, except for backwards compatibility. Even though systemd itself makes an effort to support this, many other tools aren't as careful. Despite those efforts, we (collectively) get it wrong often, because doing it "wrong" on systems with merged-usr has no consequences. Since almost all developers are on such systems, any issues are only discovered late. Supporting this split-usr mode makes both code and documentation more complicated. The split is purely artificial and has no justification except to allow old installation to not update. Mechanisms to update existing systems are available though: Fedora did that in https://fedoraproject.org/wiki/Features/UsrMove, Debian has the usrmerge package. The next version of Debian will only support systems with split-usr=false, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=978636#178: The Technical Committee resolves that Debian 'bookworm' should support only the merged-usr root filesystem layout, dropping support for the non-merged-usr layout. Let's start warning if split-usr mode is used, in preparation to removing the split in one of the future releases.
* | | Translated using Weblate (Swedish) (#18457)Weblate (bot)2021-02-041-132/+63
| | | | | | | | | | | | | | | | | | | | | Currently translated at 94.1% (178 of 189 strings) Co-authored-by: Göran Uddeborg <goeran@uddeborg.se> Translate-URL: https://translate.fedoraproject.org/projects/systemd/master/sv/ Translation: systemd/main
* | | network: correct name of parameter in function prototypeKevin P. Fleming2021-02-031-1/+1
| | | | | | | | | | | | | | | The output parameter of `sd_rtnl_message_neigh_get_ifindex` is called `index`, not `family`.
* | | Merge pull request #18319 from yuwata/udev-move-tx-rx-queuesYu Watanabe2021-02-0313-126/+102
|\ \ \ | | | | | | | | network,udev: move TransmitQueues=/ReceiveQueues= from .network to .link
| * | | network,udev: move TransmitQueues=/ReceiveQueues= from .network to .linkYu Watanabe2021-02-0313-123/+99
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As the settings are mostly hardware setup, and merely see from network layer. See also discussions in https://github.com/systemd/systemd/pull/18170#issuecomment-758807497 https://github.com/orgs/systemd/teams/systemd/discussions/1
| * | | udev: rename TxQueueLength= -> TransmitQueueLength=Yu Watanabe2021-02-034-4/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As we usually (unfortunately not always though) do not use abbreviations. Tx may be standard abbreviation, but we already have e.g. TransmitChecksumOffload=. So, let's use Transmit instead of Tx. Follow-up for ef4a91a7e8d8337a9d65177b09eb7580b25b8f5d.
* | | | logind: simplify flags handling a bitLennart Poettering2021-02-031-12/+18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let's split out the two codepaths a bit, and emphasize which ones it the new-style and which the old-style codepath, and let's clearly convert the params of the old-stye into the new style for further processing, so that the old style path is brief and isolated. No change in behaviour. Follow-up for: 8885fed4e3a52cf1bf105e42043203c485ed9d92
* | | | Merge pull request #18423 from DaanDeMeyer/sd-boot-no-includeYu Watanabe2021-02-0318-257/+355
|\ \ \ \ | |/ / / |/| | | More sd-boot cleanups
| * | | boot: Add startswith() and endswith() functions with no_case variantsDaan De Meyer2021-02-023-12/+66
| | | | | | | | | | | | | | | | Adapted from string-util
| * | | boot: Drop unnecessary bracesDaan De Meyer2021-02-021-2/+1
| | | |
| * | | boot: Fix void pointer arithmetic warningDaan De Meyer2021-02-021-1/+1
| | | |
| * | | boot: Replace raw efivar gets with typed variantsDaan De Meyer2021-02-021-21/+15
| | | |
| * | | boot: Add efivar_get/set_uint64_le() functionsDaan De Meyer2021-02-022-0/+65
| | | | | | | | | | | | | | | | | | | | | | | | These are implemented as bit-shifting functions that allow reading and writing UEFI variables stored as little endian 64-bit unsigned values.
| * | | boot: Rename efivar_get/set_int() to efivar_get/set_uint_string()Daan De Meyer2021-02-023-9/+9
| | | | | | | | | | | | | | | | | | | | Let's clearly indicate that these are used to set/get uints that are stored as strings.
| * | | boot: Tighten scope of variables used in loopsDaan De Meyer2021-02-029-101/+70
| | | |
| * | | boot: Add efivar_get_boolean_u8()Daan De Meyer2021-02-023-5/+17
| | | |
| * | | boot: Make all efivar util functions take the guid as an argumentDaan De Meyer2021-01-314-44/+50
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Let's make these functions a little more generic so we can have them work on more than one GUID. More specifically, this allows using them with the global guid which will be used a bit more to extend the secure boot support.
| * | | boot: Turn all guid constants into C99 compound initializersDaan De Meyer2021-01-3110-60/+56
| | | | | | | | | | | | | | | | | | | | Avoids having to use the address operator all the time and avoids having to cast or do other unintuitive stuff.
| * | | boot: Enable C99Daan De Meyer2021-01-311-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Instead of using -nostdinc, we use -nostdlib. This is necessary to allow moving to C99 as efibind.h includes stdint.h when C99 is enabled. It isn't necessarily problematic to use some standard library headers as long as they don't contain functions defined in libc or another system library (or in other words, header only headers are fine to use in sd-boot).
| * | | boot: Move Secure Boot logic to new fileDaan De Meyer2021-01-318-27/+30
| | | |
* | | | ci: build with -Werror on FedoraFrantisek Sumsal2021-02-021-2/+12
| | | | | | | | | | | | | | | | Prompted by: https://github.com/systemd/systemd/pull/18400#issuecomment-771602705
* | | | path-util: tighten path_extract_filename()Lennart Poettering2021-02-022-15/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Let's tighten the logic behind path_extract_filename() a bit: first of all, refuse all cases of invalid paths with -EINVAL. More importantly though return a recognizable error when a valid path is specified that does not contain any filename. Specifically, "/" will now result in -EADDRNOTAVAIL. This changes API, but none of the existing callers care about the return value, hence the change should be fine.
* | | | Merge pull request #18435 from keszybz/oomd-readiness-and-other-tweaksLuca Boccassi2021-02-026-39/+59
|\ \ \ \ | | | | | | | | | | Mark oomd as supported and other tweaks
| * | | | meson: use ellipses for rangesZbigniew Jędrzejewski-Szmek2021-02-021-2/+2
| | | | | | | | | | | | | | | | | | | | C.f. 1d3a473b4a0a4a0c49963297103af16ff6d841fa.
| * | | | meson: take oomd out of the doghouseZbigniew Jędrzejewski-Szmek2021-02-022-9/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It's on by default in Fedora 34 [1], so we can't say it's just a preview. [1] https://fedoraproject.org/wiki/Changes/EnableSystemdOomd
| * | | | man: move content from the wiki to systemd.preset(5)Zbigniew Jędrzejewski-Szmek2021-02-023-26/+55
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The wiki was slightly stale, and almost all the information there was already present in the man page. I moved the remaing part (discussion) into the man page and adjusted all links to point to the man page instead. daemon(7) has a some examples of packaging scriptlets… I don't think it fits there very well. Most likely they should be moved to systemd.preset(5) or maybe even removed, but I'm leaving that for later.
| * | | | meson: remove one more instance of install_dir:bindirZbigniew Jędrzejewski-Szmek2021-02-021-2/+1
| | | | | | | | | | | | | | | | | | | | bindir is the default, c.f. a1fd722b5df83e526cb5feb3fb271ffe1d903472.
* | | | | Merge pull request #18432 from yuwata/libude-list-cleanupsLennart Poettering2021-02-021-11/+8
|\ \ \ \ \ | |/ / / / |/| | | | libudev: cleanups for libudev-list
| * | | | libudev: add one more assertionYu Watanabe2021-02-021-0/+1
| | | | |
| * | | | libudev: unset uptodate flag before free()ing entriesYu Watanabe2021-02-021-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | udev_list_entry_free() also removes the entry from LIST if the flag is set. This slightly optimizes the cleanup logic.
| * | | | libudev: also drop the entry from LIST even if unique flag is setYu Watanabe2021-02-021-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Otherwise, the list becomes dirty when an entry is freed. This also remove the entry from the hashmap only when its name is set. The name should be always set, so that does not change anything. But just for safety.
View Lorry Controller Status