summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* networkd: route - add expiration supportTom Gundersen2015-10-303-7/+65
| | | | | | This should really live in the kernel, but the netlink API currently does not support it. Until support has been added, expire the route from userspace.
* networkd: link - deserialize routesTom Gundersen2015-10-301-0/+43
|
* networkd: link - (de)serialize IPv4LL and DHCPv4 addressesTom Gundersen2015-10-303-11/+73
| | | | | This initializes the clients to try rebinding the preexisting addresses before doing anything else.
* networkd: link - deserializeTom Gundersen2015-10-304-19/+111
| | | | | | | For now only deserialize some basic state and the applied addresses. When a link is added, try to deserialize it's state from /run. This is relevant only when networkd is restarted at runtime.
* networkd: link - serialize routesTom Gundersen2015-10-301-0/+17
|
* networkd: route - track routesTom Gundersen2015-10-307-2/+419
|
* networkd: address - properly take over a foreign addressTom Gundersen2015-10-301-5/+29
|
* networkd: address - update link operstate when address is updatedTom Gundersen2015-10-301-2/+6
| | | | | The operstate may change based on address properties, so make a change of address trigger an operstate update.
* networkd: route - clean up confusion between 'metric' and 'priority'Tom Gundersen2015-10-305-14/+12
| | | | | Different tools use different terms for the same concept, let's try to stick with 'priority', as that is what the netlink API uses.
* networkd: route - rename fields in structTom Gundersen2015-10-305-50/+50
|
* Merge pull request #1720 from evverx/shell-completion-global-modeDaniel Mack2015-10-301-0/+2
|\ | | | | shell-completion: systemctl: show completions for `user` in `global` …
| * shell-completion: systemctl: show completions for `user` in `global` modeEvgeny Vereshchagin2015-10-301-0/+2
| |
* | hwdb: Update database of Bluetooth company identifiersMarcel Holtmann2015-10-301-0/+84
|/
* Merge pull request #1709 from evverx/set-location-completionDaniel Mack2015-10-291-1/+1
|\ | | | | shell-completion: hostnamectl: add the command set-location
| * shell-completion: hostnamectl: add the command set-locationEvgeny Vereshchagin2015-10-291-1/+1
| |
* | Merge pull request #1717 from ronnychevalier/rc/test_capabilityboundingset2Daniel Mack2015-10-295-2/+53
|\ \ | | | | | | test: add tests to ensure that the capabilities are properly set
| * | test: add tests to ensure that the capabilities are properly setRonny Chevalier2015-10-295-2/+53
|/ /
* | Merge pull request #1713 from evverx/test-cap-bounding-set-mergingRonny Chevalier2015-10-292-1/+47
|\ \ | |/ |/| Another fix of the CapabilityBoundingSet parsing
| * core: fix capability bounding set parsingEvgeny Vereshchagin2015-10-291-1/+1
| | | | | | | | bug: CapabilityBoundingSet= doesn't reset all caps
| * test: add test for capability bounding set parsingEvgeny Vereshchagin2015-10-291-0/+46
|/
* Merge pull request #1700 from ssahani/wordLennart Poettering2015-10-283-24/+31
|\ | | | | Port to extract_first_word
| * nspwan: port to extract_first_wordSusant Sahani2015-10-281-7/+9
| |
| * install: port to extract_first_wordSusant Sahani2015-10-281-9/+10
| |
| * journal-remote: port to extract_first_wordSusant Sahani2015-10-281-8/+12
| |
* | Merge pull request #1707 from dvdhrm/notify-prioLennart Poettering2015-10-281-79/+77
|\ \ | | | | | | core: fix priority ordering in notify-handling
| * | core: fix priority ordering in notify-handlingDavid Herrmann2015-10-281-79/+77
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Currently, we dispatch NOTIFY messages in a tight loop. Regardless how much data is incoming, we always dispatch everything that is queued. This, however, completely breaks priority event-handling of sd-event. When dispatching one NOTIFY event, another completely different event might fire, or might be queued by the NOTIFY handling. However, this event will not get dispatched until all other further NOTIFY messages are handled. Those might even arrive _after_ the other event fired, and as such completely break priority ordering of sd-event (which several code paths rely on). Break this by never dispatching multiple messages. Just return after each message that was read and let sd-event handle everything else. (The patch looks scarier that it is. It basically just drops the for(;;) loop and re-indents the loop-content.)
* | | Merge pull request #1705 from filbranden/testutil1Lennart Poettering2015-10-285-940/+1025
|\ \ \ | | | | | | | | Move tests for extract-word and parse-util into separate test cases
| * | | test-parse-util: Move parse-util tests into their own test caseFilipe Brandenburger2015-10-284-419/+460
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Tests for the functions defined in src/basic/parse-util.c. Reorder them to match the order in which the functions are defined in the source file. Adjusted the list of include files to remove the ones no longer needed in test-util.c. Tested that `make check` still passes as expected. Also checked the number of lines removed from test-util.c matches the expected, as an additional verification that no tests were dropped or duplicated in the move.
| * | | test-extract-word: Move extract-word tests into their own test caseFilipe Brandenburger2015-10-284-510/+554
| | | | | | | | | | | | | | | | | | | | | | | | Tests for the functions defined in src/basic/extract-word.c. Tested that `make check` still passes as expected.
| * | | build-sys: Keep .gitignore sortedFilipe Brandenburger2015-10-281-11/+11
|/ / / | | | | | | | | | Let's try to keep it that way! :-)
* | | Merge pull request #1703 from ronnychevalier/rc/test_execute_check_nobody2Lennart Poettering2015-10-281-3/+9
|\ \ \ | | | | | | | | test-execute: check if nobody exists before running some tests
| * | | test-execute: check if nobody exists before running some testsRonny Chevalier2015-10-281-3/+9
| |/ /
* | | Merge pull request #1699 from filbranden/cpuaffinity9Lennart Poettering2015-10-286-21/+304
|\ \ \ | |/ / |/| | cpu-set-util: Support ranges in parse_cpu_set_and_warn (v4)
| * | man: Update man page documentation for CPUAffinityFilipe Brandenburger2015-10-282-4/+8
| | | | | | | | | | | | | | | | | | | | | Document support for commas as a separator and possibility of specifying ranges of CPU indices. Tested by regenerating the manpages locally and reading them on man.
| * | cpu-set-util: Support ranges in parse_cpu_set_and_warnFilipe Brandenburger2015-10-282-14/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | Tested CPUAffinity ranges on both a service unit and in system.conf and confirmed they work as expected (by inspecting /proc/PID/status, for the main pid of the service and for pid 1). Also mixed ranges with both spaces, commas, trailing commas and spaces. Added new tests to increase coverage of ranges and prevent regressions.
| * | parse-util: Introduce new parse_range functionFilipe Brandenburger2015-10-283-0/+220
| | | | | | | | | | | | | | | | | | | | | This function will be useful for CPUAffinity settings that involve ranges of CPUs. Make it generic and include test coverage to prevent regressions.
| * | cpu-set-util: Accept commas as separators in parse_cpu_set_and_warnFilipe Brandenburger2015-10-282-3/+16
| |/ | | | | | | | | | | | | | | Tested CPUAffinity settings on both a service unit and in system.conf and confirmed they work as expected. Added a new test to confirm that trailing commas and spaces work and to prevent any regressions in that area.
* | Merge pull request #1701 from hosiet/l10n-cnDaniel Mack2015-10-284-0/+782
|\ \ | |/ |/| l10n: add Simplified Chinese translation.
| * l10n: add zh_CN translation.Boyuan Yang2015-10-284-0/+782
|/
* Merge pull request #1698 from poettering/pid-is-unwaited-fixTom Gundersen2015-10-275-78/+77
|\ | | | | fixup for previous pr
| * service: exiting early is nicer than deeply-indented code blocksLennart Poettering2015-10-271-49/+48
| |
| * core: all unit types that watch control PIDs should use the same logicLennart Poettering2015-10-274-31/+29
| | | | | | | | | | | | When coldplugging the unit state, make sure to follow the same basic logic for all unit types: always verify whether the control PID is still a waitable process before proceeding.
| * core: don't pass uninitialzed PIDs to pid_is_unwaited()Lennart Poettering2015-10-271-2/+4
| | | | | | | | | | | | | | | | | | | | Since 5fd9b2c5467b0a42ccdabc7eb8e516d512609a8e passing a pid of 0 to pid_is_unwaited() and pid_is_live() is considered as a request on the current process, similar how the other calls in process-util.c handle a PID of 0. This broke service.c, which passes a 0 PID and expects it to be considered an unwaited process. This fix make sure we can boot again.
* | Merge pull request #1695 from evverx/fix-cap-bounding-mergingLennart Poettering2015-10-271-3/+5
|\ \ | |/ |/| core: fix CapabilityBoundingSet merging
| * core: fix CapabilityBoundingSet mergingEvgeny Vereshchagin2015-10-271-3/+5
| | | | | | | | Fixes: #1221
* | Merge pull request #1691 from poettering/util-lib-3Tom Gundersen2015-10-27503-4802/+6781
|\ \ | |/ |/| split up util.h and macro.h into even more bits
| * util-lib: move inotify-related definitions to fs-util.[ch]Lennart Poettering2015-10-276-15/+21
| |
| * util-lib: move fdname_is_valid() to fd-util.[ch]Lennart Poettering2015-10-274-29/+29
| |
| * automount: move generically userful call repeat_mount() into mount-util.[ch]Lennart Poettering2015-10-273-22/+37
| |
| * process-util: move a couple of process-related calls overLennart Poettering2015-10-2713-145/+158
| |