summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * | network: rename SendOptions= to SendOption=Zbigniew Jędrzejewski-Szmek2019-10-305-6/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | The name with plural made more sense where multiple options could be specified in one line. After changes in the pull request, this option only accepts one value, so from users' POV it should be singular. (The field in the data structure remains plural, because it actually stores multiple values.)
* | | NEWS: fix option nameYu Watanabe2019-10-301-1/+1
| | |
* | | Merge pull request #13879 from keszybz/news-v244Yu Watanabe2019-10-304-0/+152
|\ \ \ | | | | | | | | NEWS for v244
| * | | network: install wifi-adhoc.network by default, make wifi-{ap,station} examplesZbigniew Jędrzejewski-Szmek2019-10-303-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | I think 80-wifi-adhoc.network is safe enough, since it just enables the link-local addressing. But the other two enable DHCP in client or server modes, and we should not do this by default.
| * | | NEWS: start preparations for v244Zbigniew Jędrzejewski-Szmek2019-10-301-0/+149
| | | |
* | | | Merge pull request #13866 from keszybz/nspawn-restartsLennart Poettering2019-10-3013-25/+122
|\ \ \ \ | |/ / / |/| | | Make 'machinectl reboot' functional
| * | | machined: only Unref units that we AddRef'dZbigniew Jędrzejewski-Szmek2019-10-292-3/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | b92d0b4c5adef37e9de8f6cc22a0e27b97fcf3ad added AddRef to the StartTransientUnit call in machine_start_scope()/manager_start_scope() and a corresponding Unref call in machine_stop_scope(). But when we are running systemd-nspawn@ with --keep unit, the unit is not created by machined so the AddRef never happens. Then when trying to stop the unit, we'd get: systemd-machined[1101]: Sent message type=method_call sender=n/a destination=org.freedesktop.systemd1 path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager member=UnrefUnit cookie=37 reply_cookie=0 signature=s error-name=n/a error-message=n/a systemd-machined[1101]: Got message type=error sender=:1.1 destination=:1.13 path=n/a interface=n/a member=n/a cookie=2443 reply_cookie=37 signature=s error-name=org.freedesktop.systemd1.NotReferenced error-message=Unit has not been referenced yet. systemd-machined[1101]: Failed to drop reference to machine scope, ignoring: Unit has not been referenced yet.
| * | | shared/logs-show: strip trailing carriage returns at EOL/EOFZbigniew Jędrzejewski-Szmek2019-10-293-5/+38
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When showing logs from a container, we would fail to show various lines: Oct 29 09:50:51 krowka systemd-nspawn[61376]: Detected architecture x86-64. Oct 29 09:50:51 krowka systemd-nspawn[61376]: [1B blob data] Oct 29 09:50:51 krowka systemd-nspawn[61376]: Welcome to Fedora 32 (Rawhide)! Oct 29 09:50:51 krowka systemd-nspawn[61376]: [1B blob data] Those are only harmless \r characters that trail the line. We already replace tabs and strip various ansi characters that we deem inconsequential, so let's also strip trailing carriage returns. Non-trailing ones are different, because they change what would be displayed.
| * | | nspawn: when stopping the machine, just deregister the machineZbigniew Jędrzejewski-Szmek2019-10-293-10/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We already shut the machine down ourselves (and pid1 will also do cleanup for us after we exit if anything was left behind). No need for systemd-machined to try to stop the unit too. (This calls the new machined method. If we are running against an older machined, we will not deregister the machine. If we are simply exiting, machined should notice that the unit is gone on its own. If we are restarting, we will fail to register the machine after restart and fail. But this case was already broken, because machined would create a stop job, breaking the restart. So not doing anything with old machined should not make anything more broken than it already is.) Fixes #13766.
| * | | machined: add UnregisterMachine methodZbigniew Jędrzejewski-Szmek2019-10-295-1/+42
| | | | | | | | | | | | | | | | | | | | | | | | This is the opposite of RegisterMachine: machined knows that the machine is "gone", but doesn't do anything on its own. We already had TerminateMachine, but that would stop the unit, which isn't always wanted.
| * | | pid1: log the reason why restart will or will not happenZbigniew Jędrzejewski-Szmek2019-10-291-6/+24
| | | | | | | | | | | | | | | | | | | | I was trying to figure out why the restart was not happening, and it wasn't at all obvious. Let's add a nice debug message.
* | | | coverity: replace python with jqEvgeny Vereshchagin2019-10-302-4/+4
| |/ / |/| | | | | | | | | | | | | | | | | | | | Judging by https://travis-ci.org/systemd/systemd/jobs/604425785 (where the script failed with "tools/coverity.sh: line 45: python: command not found") python-unversioned-command is no longer installed by default with python2. Given that it's not the first time python has vanished and it's not clear what exactly should be installed to make sure it's there, let's just use jq instead.
* | | Merge pull request #13747 from ssahani/tc-qdiscYu Watanabe2019-10-3021-4/+1942
|\ \ \ | | | | | | | | network: introduce Traffic Control
| * | | test-network: add tests for qdiscYu Watanabe2019-10-302-3/+35
| | | |
| * | | network: wait for QDiscs to be configuredYu Watanabe2019-10-303-4/+36
| | | |
| * | | network: introduce TrafficControlSusant Sahani2019-10-3019-1/+1875
| | |/ | |/| | | | | | | Add network delay to a interface
* | | Merge pull request #13867 from keszybz/man-conditionYu Watanabe2019-10-302-358/+418
|\ \ \ | |/ / |/| | Refactor description of conditons
| * | man: reword description of triggering conditionsZbigniew Jędrzejewski-Szmek2019-10-291-7/+7
| | | | | | | | | | | | Fixes #13758.
| * | man: split out description of Conditions and Assert to new sectionZbigniew Jędrzejewski-Szmek2019-10-291-357/+417
| | | | | | | | | | | | | | | | | | | | | We slowly added many many conditions over the years, and the text became very hard to read, because all the terms were squished in one <termitem>. This rearragnes the text into a new subsection, with minimal grammar changes and removal of repetitions.
| * | shared: small typoZbigniew Jędrzejewski-Szmek2019-10-281-1/+1
| | |
* | | Merge pull request #13676 from ClydeByrdIII/service-result-patchAnita Zhang2019-10-291-1/+16
|\ \ \ | | | | | | | | Update service result table
| * | | Update service result tableClydeByrdIII2019-09-281-1/+16
| | | | | | | | | | | | | | | | | | | | exec-condition and oom-kill were added without updating this table Updated success to reflect the code, which also allows kills by signal in certain situations
* | | | boot-loader-spec: add devicetree-overlay keyMichael Tretter2019-10-291-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Device tree overlays are a convenient way to patch device trees, e.g., add new devices to a device tree or enable/disable devices. This is useful for non-discoverable but configurable hardware. Device tree overlays are commonly used for displays on the Raspberry Pi or for describing the content of FPGA bitstreams. Add the devicetree-overlay key to boot loader specification entries to allow boot loaders to apply overlays. See #13537
* | | | Merge pull request #13864 from fbuihuu/no-more-swap-autoactivationZbigniew Jędrzejewski-Szmek2019-10-295-23/+12
|\ \ \ \ | | | | | | | | | | No more swap autoactivation
| * | | | core: drop 'wants' parameter from unit_add_node_dependency()Franck Bui2019-10-285-18/+8
| | | | | | | | | | | | | | | | | | | | | | | | | Since Wants dependency is no more automagically added to swap and mount units, this parameter is no more used hence this patch drops it.
| * | | | swap: do not make swap units wanted by its device unit anymoreFranck Bui2019-10-281-6/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It was done for mount units already (see commit 142b8142d7bb84f07). For the same reasons and for consistency we should also stop activating automagically swaps when their device is hot-plugged.
* | | | | network-generator: Add missing help for --rootDavid Pedersen2019-10-291-0/+1
|/ / / /
* | | | Merge pull request #13423 from pwithnall/12035-session-time-limitsZbigniew Jędrzejewski-Szmek2019-10-2811-18/+135
|\ \ \ \ | | |_|/ | |/| | Add `RuntimeMaxSec=` support to scope units (time-limited login sessions)
| * | | pam_systemd: Forward systemd.runtime_max_sec setting to session scopePhilip Withnall2019-10-282-3/+36
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Allow earlier PAM modules to set `systemd.runtime_max_sec`. If they do, parse it and set it as the `RuntimeMaxUSec=` property of the session scope, to limit the maximum lifetime of the session. This could be useful for time-limiting login sessions, for example. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #12035
| * | | scope: Support RuntimeMaxSec= directive in scope unitsPhilip Withnall2019-10-289-2/+65
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Just as `RuntimeMaxSec=` is supported for service units, add support for it to scope units. This will gracefully kill a scope after the timeout expires from the moment the scope enters the running state. This could be used for time-limited login sessions, for example. Signed-off-by: Philip Withnall <withnall@endlessm.com> Fixes: #12035
| * | | scope: Refactor timer handling on coldplugPhilip Withnall2019-07-291-5/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Factor it out into a helper function which is a bit easier to expand in future. This introduces no functional changes. Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | | shared: Factor out bus_append_scope_property() for scopesPhilip Withnall2019-07-291-4/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This introduces no functional changes, but will make some upcoming changes a little clearer. Signed-off-by: Philip Withnall <withnall@endlessm.com>
| * | | dbus-scope: Factor out common UNIT(s) castPhilip Withnall2019-07-291-4/+5
| | | | | | | | | | | | | | | | | | | | | | | | This introduces no functional changes. Signed-off-by: Philip Withnall <withnall@endlessm.com>
* | | | modules-load: do not fail service if modules are not presentZbigniew Jędrzejewski-Szmek2019-10-281-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | It is pretty common for the service to fail in the initramfs (for example because certain modules have not been copied over or haven't been built yet in case of dkms modules). This seems to be more trouble than it is worth. Let's change the service to simply log any missing modules at error level, but not fail the whole service. https://bugzilla.redhat.com/show_bug.cgi?id=1254340
* | | | Merge pull request #13844 from keszybz/resolved-proprtiesYu Watanabe2019-10-289-19/+42
|\ \ \ \ | | | | | | | | | | Emit dbus PropertyChanged notifications for systemd-resolved
| * | | | resolved: emit change for CurrentDNSServerZbigniew Jędrzejewski-Szmek2019-10-252-1/+4
| | | | |
| * | | | resolved: emit change for LLMNRHostnameZbigniew Jędrzejewski-Szmek2019-10-252-2/+6
| | | | |
| * | | | resolved: send out notifications about DNS propertyZbigniew Jędrzejewski-Szmek2019-10-254-1/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Notifications are only sent for the top object, and not for individual links. This should be enough for the most obvious cases where somebody just cares about the effective set of servers. Fixes #13721.
| * | | | resolved: make two functions staticZbigniew Jędrzejewski-Szmek2019-10-252-5/+2
| | | | |
| * | | | resolved: one less {}Zbigniew Jędrzejewski-Szmek2019-10-251-2/+1
| | | | |
| * | | | resolved: avoid allocationZbigniew Jędrzejewski-Szmek2019-10-254-8/+7
| | | | | | | | | | | | | | | | | | | | While at it, constify the argument.
* | | | | pid1: order .automount units after local-fs-pre.targetZbigniew Jędrzejewski-Szmek2019-10-281-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From the bug: > According to the documentation of systemd.automount if the automoint point is > automagically created if it doesn't exist yet. This ofcourse means the > filesystem underneath has to be writable, which for / means not only does > -.mount need to be started but also systemd-remount-fs.service has to be run, > which isn't guaranteed by the default automount dependencies. > > For .mount units there is an automatic default After= dependency on > local-fs-pre.target, would probably make sense to do the same for automount > units to avoid it failing on the corner-case where it has to create directory. Fixes #13306.
* | | | | Merge pull request #13635 from fbuihuu/no-aliases-with-enableZbigniew Jędrzejewski-Szmek2019-10-283-7/+9
|\ \ \ \ \ | |_|_|_|/ |/| | | | man: alias names can't be used with enable command
| * | | | shared/install: failing with -ELOOP can be due to the use of an alias in ↵Franck Bui2019-09-241-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | install_error() -ELOOP can happen also when enabling an alias name (which is admittedly useless since the unit it belongs to was already enabled) so let's mention this possibility when reporting the corresponding error.
| * | | | shared/install: fix error codes returned by install_context_apply()Franck Bui2019-09-241-1/+1
| | | | |
| * | | | man: alias names can't be used with enable commandFranck Bui2019-09-241-4/+4
| | | | |
* | | | | po: update Polish translationPiotr Drąg2019-10-261-2/+20
| | | | |
* | | | | meson: expand ternary in functions to if statementsAnita Zhang2019-10-261-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Per https://github.com/mesonbuild/meson/issues/5003, ternary doesn't always work as function args with older versions of meson. Expand out ternary statements to stay compatible with older versions (< 0.49).
* | | | | Merge pull request #13846 from keszybz/sleep-config-fixupsAnita Zhang2019-10-251-16/+16
|\ \ \ \ \ | | | | | | | | | | | | Sleep config fixups
| * | | | | shared/sleep-config: two more error handling fixes, use structured ↵Zbigniew Jędrzejewski-Szmek2019-10-251-13/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | initialization CID#1406472.
View Lorry Controller Status