Re: [systemd-devel] [PATCH] fix typos in systemd-nspawn man page
Hi On Sat, May 23, 2015 at 5:11 AM, Jonathan Boulle jonathan.bou...@coreos.com wrote: --- man/systemd-nspawn.xml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) Applied! Thanks David diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index 6a5db86cec3c..06285edc0bb3 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -330,7 +330,7 @@ first host UID to assign to the container, the second parameter specifies the number of host UIDs to assign to the container. If the second parameter is omitted, 65536 UIDs are -assigned. If the first parameter is also ommitted (and hence +assigned. If the first parameter is also omitted (and hence no parameter passed at all), the first UID assigned to the container is read from the owner of the root directory of the container's directory tree. By default no user namespacing is @@ -454,7 +454,7 @@ container port number in the range from 1 to 65535. The protocol specifier and its separating colon may be omitted, in which case literaltcp/literal is assumed. The container -port number and its colon may be ommitted, in which case the +port number and its colon may be omitted, in which case the same port as the host port is implied. This option is only supported if private networking is used, such as option--network-veth/option or -- 1.9.3 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to wait for specific interface/IP?
On Sat, May 23, 2015 at 1:03 PM, Ian Pilcher arequip...@gmail.com wrote: Is there a simple way to make a service require that a specific network interface/IP address be active? You have to wait for the *link* to be active, not for the interface.. I have a manually set up bridge and dnsmasq configuration for my VM traffic, but dnsmasq is getting started before NetworkManager has configured the bridge and failing because it cannot bind to the bridge's IP address. This is problem has more than one face.. 1) Enable the NetworkManager-wait-online service 2) order dnsmasq after the network-online target. But this is all a workaround.. you could configure dnsmasq not to fail to bind on interfaces that are not yet available at the point the daemon is started. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] How to wait for specific interface/IP?
On Sat, May 23, 2015 at 7:03 PM, Ian Pilcher arequip...@gmail.com wrote: Is there a simple way to make a service require that a specific network interface/IP address be active? I have a manually set up bridge and dnsmasq configuration for my VM traffic, but dnsmasq is getting started before NetworkManager has configured the bridge and failing because it cannot bind to the bridge's IP address. dnsmasq has the bind-dynamic option for such situations. -- Mantas Mikulėnas graw...@gmail.com ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] How to wait for specific interface/IP?
Is there a simple way to make a service require that a specific network interface/IP address be active? I have a manually set up bridge and dnsmasq configuration for my VM traffic, but dnsmasq is getting started before NetworkManager has configured the bridge and failing because it cannot bind to the bridge's IP address. TIA! -- Ian Pilcher arequip...@gmail.com I grew up before Mark Zuckerberg invented friendship ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] [PATCH] core: if PR_SET_CHILD_SUBREAPER fails, log_error instead of warning
It was a warning when we still supported kernel 3.4. current
minimum version is 3.7.
---
src/core/main.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/src/core/main.c b/src/core/main.c
index c39815b..3bebc98 100644
--- a/src/core/main.c
+++ b/src/core/main.c
@@ -1608,9 +1608,7 @@ int main(int argc, char *argv[]) {
if (arg_running_as == MANAGER_USER) {
/* Become reaper of our children */
if (prctl(PR_SET_CHILD_SUBREAPER, 1) 0) {
-log_warning_errno(errno, Failed to make us a
subreaper: %m);
-if (errno == EINVAL)
-log_info(Perhaps the kernel version is too
old ( 3.4?));
+log_error_errno(errno, Failed to make us a subreaper:
%m);
}
}
--
2.4.1
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [PATCH] core: if PR_SET_CHILD_SUBREAPER fails, log_error instead of warning
Patchset imported to github. Pull request: https://github.com/systemd-devs/systemd/compare/master...systemd-mailing-devs:1432397052-3806-1-git-send-email-crrodriguez%40opensuse.org -- Generated by https://github.com/haraldh/mail2git ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] Problem when m-finish_timestamp is set before running manager_loop
2015-05-22 3:36 GMT+08:00 Lennart Poettering lenn...@poettering.net: Should be fixed in git. Please verify! Confirmed, thanks! -- Regards, - cee1 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
