El 18/02/14 11:27, Zbigniew Jędrzejewski-Szmek escribió:
On Tue, Feb 18, 2014 at 10:56:36AM -0300, Cristian Rodríguez wrote:
SECCOMP_CFLAGS must be in the global CFLAGS as is
included in core/execute.h. when seccomp.h is not in the standard
path.(i.e openSUSE has it in /usr/include/pkg/libsecco
From: Thomas Hindoe Paaboel Andersen
Add:
--system
-H --host
-M --machine
--service-type (options: simple forking oneshot dbus notify idle)
--uid
--gid
--nice
--setenv
---
The last 5 are not documented in the man page. The options for --service-type
are my guess. Please review.
shell-completio
On Fri, Feb 21, 2014 at 8:54 PM, Thomas H.P. Andersen wrote:
> From: Thomas Hindoe Paaboel Andersen
>
> ---
> Not too sure about the bridge -> netdev change. It just seemed a strange to
> read
> since we set the type a bit later to be either bridge, bond, or vlan.
>
> man/systemd-networkd.servi
From: Thomas Hindoe Paaboel Andersen
---
Not too sure about the bridge -> netdev change. It just seemed a strange to read
since we set the type a bit later to be either bridge, bond, or vlan.
man/systemd-networkd.service.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Fri, Feb 21, 2014 at 07:25:50PM +, "Jóhann B. Guðmundsson" wrote:
>
> On 02/21/2014 06:34 PM, Greg KH wrote:
> >On Fri, Feb 21, 2014 at 06:23:25PM +, "Jóhann B. Guðmundsson" wrote:
> >>Greetings
> >>
> >>What are the current plans for Infiniband network (IPoIB) support in
> >>networkd?
On 02/21/2014 06:34 PM, Greg KH wrote:
On Fri, Feb 21, 2014 at 06:23:25PM +, "Jóhann B. Guðmundsson" wrote:
Greetings
What are the current plans for Infiniband network (IPoIB) support in networkd?
Why wouldn't it "just work" today? Have you tried it? If so, what is
missing?
Nope not tri
On Thu, 20.02.14 23:25, Paul Menzel (paulepan...@users.sourceforge.net) wrote:
> Dear systemd folks,
>
>
> Docker, “an open-source project to easily create lightweight, portable,
> self-sufficient containers from any application”, [1] mostly recommends
> to use Supervisor [2] to control the proc
On Fri, Feb 21, 2014 at 06:23:25PM +, "Jóhann B. Guðmundsson" wrote:
> Greetings
>
> What are the current plans for Infiniband network (IPoIB) support in networkd?
Why wouldn't it "just work" today? Have you tried it? If so, what is
missing?
thanks,
greg k-h
__
Hi Jóhann,
On Fri, Feb 21, 2014 at 7:23 PM, "Jóhann B. Guðmundsson"
wrote:
> What are the current plans for Infiniband network (IPoIB) support in
> networkd?
There are no plans for that at the moment.
Cheers,
Tom
___
systemd-devel mailing list
system
Greetings
What are the current plans for Infiniband network (IPoIB) support in
networkd?
JBG
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On Fri, Feb 21, 2014 at 06:00:46PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
> On Fri, Feb 21, 2014 at 11:22:50AM -0500, Dave Reisner wrote:
> > Prior to 3.2, /proc/sys/kernel/hostname isn't a pollable file and
> > sd_event_add_io will return EPERM. Ignore this failure, since it isn't
> > critical
It was <2014-02-21 pią 17:06>, when Kay Sievers wrote:
> On Fri, Feb 21, 2014 at 4:58 PM, Łukasz Stelmach
> wrote:
>> It was <2014-02-21 pią 16:22>, when Lennart Poettering wrote:
>>> On Fri, 21.02.14 15:54, Łukasz Stelmach (l.stelm...@samsung.com) wrote:
>>>
Fix problems with unresolved sym
On Fri, Feb 21, 2014 at 11:22:50AM -0500, Dave Reisner wrote:
> Prior to 3.2, /proc/sys/kernel/hostname isn't a pollable file and
> sd_event_add_io will return EPERM. Ignore this failure, since it isn't
> critical to journald operation.
> ---
> Reported and tested by user sraue on IRC.
This should
It was backward - --after fetches After property, so units shown really
come *before* unit given as argument. Same for --before.
---
man/systemctl.xml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/man/systemctl.xml b/man/systemctl.xml
index 355cd11..fef9578 100644
--- a/
On Fri, 21.02.14 16:51, Reindl Harald (h.rei...@thelounge.net) wrote:
> > Well I kinda get that using it for containers and such like could be
> > useful, but I also suspect it should be bus or socket activated rather
> > than statically enabled... like localed, datetimed etc. Any reason to
> > en
> True, but this requires manual patching and fixing up of `make
> install`, which is a bummer.
Why?
Your debian/rules or rpmspec %build can simply do something like this:
make install
rm -f ${DEST}/etc/systemd/system/FOOO.BAR
that is much easier than quilt patches that modify Makefile.
Prior to 3.2, /proc/sys/kernel/hostname isn't a pollable file and
sd_event_add_io will return EPERM. Ignore this failure, since it isn't
critical to journald operation.
---
Reported and tested by user sraue on IRC.
src/journal/journald-server.c | 8
1 file changed, 8 insertions(+)
diff
On Fri, 21.02.14 15:44, Colin Guthrie (gm...@colin.guthr.ie) wrote:
> 'Twas brillig, and Reindl Harald at 21/02/14 08:45 did gyre and gimble:
> >
> >
> > Am 21.02.2014 04:41, schrieb Zbigniew Jędrzejewski-Szmek:
> >> On Fri, Feb 21, 2014 at 04:00:10AM +0100, Jason A. Donenfeld wrote:
> >>> syste
Am 21.02.2014 17:03, schrieb Tom Gundersen:
>> What about Zbigniews idea of using something like:
>> ConditionDirectoryNotEmpty=/etc/systemd/network/
>>
>> Would that work?
>
> We'd have to look in all the possible folders, and there may (and due
> to 99-deafult.link, always will) be files there,
On Fri, 21.02.14 17:14, Jason A. Donenfeld (ja...@zx2c4.com) wrote:
>
> On Fri, Feb 21, 2014 at 5:11 PM, Tom Gundersen wrote:
> >
> > In the not-too-distant future we'll start shipping some configuration
> > files (as Lennart mentioned to do with nspawn). These are files that
> > in most cases w
On Fri, Feb 21, 2014 at 5:13 PM, Tom Gundersen wrote:
> You probably sent this before reading my previous answer, so sorry for
> repeating myself: there will soon be cases where (special purpose)
> config files are shipped by packages rather than written by
> administrators, which is what we want
On Fri, 21.02.14 16:31, Jason A. Donenfeld (ja...@zx2c4.com) wrote:
>
> On Fri, Feb 21, 2014 at 4:19 PM, Lennart Poettering
> wrote:
> >
> > Well, ultimately it's up the distributions to decide what they want to
> > enable and what not.
>
> True, but this requires manual patching and fixing up
On Fri, Feb 21, 2014 at 5:11 PM, Tom Gundersen wrote:
>
> In the not-too-distant future we'll start shipping some configuration
> files (as Lennart mentioned to do with nspawn). These are files that
> in most cases will not apply, and shouldn't interfere with your
> existing networking solutions,
On Fri, Feb 21, 2014 at 5:10 PM, Jason A. Donenfeld wrote:
> On Fri, Feb 21, 2014 at 5:03 PM, Tom Gundersen wrote:
>> We'd have to look in all the possible folders, and there may (and due
>> to 99-deafult.link, always will) be files there, so we don't really
>> have a reasonable test. When we sta
To clarify things:
1. Arch's script deals with 80-net-setup-link.rules
2. freedesktop.org wiki followed suit and added that suggestion
3. Others have said elsewhere that the proper way to do this is
actually to override 99-default.link instead.
4. Gentoo went with number 3.
Now:
5. Can numbers 1
On Fri, Feb 21, 2014 at 4:31 PM, Jason A. Donenfeld wrote:
> On Fri, Feb 21, 2014 at 4:19 PM, Lennart Poettering
> wrote:
>>
>> Well, ultimately it's up the distributions to decide what they want to
>> enable and what not.
>
> True, but this requires manual patching and fixing up of `make
> insta
On Fri, Feb 21, 2014 at 5:03 PM, Tom Gundersen wrote:
> We'd have to look in all the possible folders, and there may (and due
> to 99-deafult.link, always will) be files there, so we don't really
> have a reasonable test. When we start shipping some default .network
> files it becomes even harder
On 21/02/14 17:37, Colin Guthrie wrote:
> 'Twas brillig, and Zbigniew Jędrzejewski-Szmek at 21/02/14 13:58 did
> gyre and gimble:
>> On Fri, Feb 21, 2014 at 02:24:58PM +0100, Tom Gundersen wrote:
>>> On Fri, Feb 21, 2014 at 3:29 AM, Jason A. Donenfeld wrote:
Hey guys,
This commit c
On Fri, Feb 21, 2014 at 4:58 PM, Łukasz Stelmach wrote:
> It was <2014-02-21 pią 16:22>, when Lennart Poettering wrote:
>> On Fri, 21.02.14 15:54, Łukasz Stelmach (l.stelm...@samsung.com) wrote:
>>
>>> Fix problems with unresolved symbols when building on Ubuntu 12.04 x86_64.
>>>
>>> --8<-
On Fri, Feb 21, 2014 at 4:44 PM, Michael Biebl wrote:
> 2014-02-21 16:31 GMT+01:00 Jason A. Donenfeld :
>> On Fri, Feb 21, 2014 at 4:19 PM, Lennart Poettering
>> wrote:
>>>
>>> Well, ultimately it's up the distributions to decide what they want to
>>> enable and what not.
>>
>> True, but this req
It was <2014-02-21 pią 16:22>, when Lennart Poettering wrote:
> On Fri, 21.02.14 15:54, Łukasz Stelmach (l.stelm...@samsung.com) wrote:
>
>> Fix problems with unresolved symbols when building on Ubuntu 12.04 x86_64.
>>
>> --8<---cut here---start->8---
>> ./.libs
On Fri, Feb 21, 2014 at 4:36 PM, Jason A. Donenfeld wrote:
> It doesn't make any sense to symlink this unit file into /etc when the
> unit file itself isn't even installed, with --disable-networkd. This
> moves the GENERAL_ALIASES logic into the right "if" block.
Applied. Thanks!
Cheers,
Tom
__
Am 21.02.2014 16:44, schrieb Colin Guthrie:
> 'Twas brillig, and Reindl Harald at 21/02/14 08:45 did gyre and gimble:
>> Am 21.02.2014 04:41, schrieb Zbigniew Jędrzejewski-Szmek:
>>> On Fri, Feb 21, 2014 at 04:00:10AM +0100, Jason A. Donenfeld wrote:
systemd-networkd seems to get started by
'Twas brillig, and Reindl Harald at 21/02/14 08:45 did gyre and gimble:
>
>
> Am 21.02.2014 04:41, schrieb Zbigniew Jędrzejewski-Szmek:
>> On Fri, Feb 21, 2014 at 04:00:10AM +0100, Jason A. Donenfeld wrote:
>>> systemd-networkd seems to get started by default in 209. Why is this?
>>> What if I do
2014-02-21 16:31 GMT+01:00 Jason A. Donenfeld :
> On Fri, Feb 21, 2014 at 4:19 PM, Lennart Poettering
> wrote:
>>
>> Well, ultimately it's up the distributions to decide what they want to
>> enable and what not.
>
> True, but this requires manual patching and fixing up of `make
> install`, which i
'Twas brillig, and Zbigniew Jędrzejewski-Szmek at 21/02/14 13:58 did
gyre and gimble:
> On Fri, Feb 21, 2014 at 02:24:58PM +0100, Tom Gundersen wrote:
>> On Fri, Feb 21, 2014 at 3:29 AM, Jason A. Donenfeld wrote:
>>> Hey guys,
>>>
>>> This commit caught me by surprise:
>>>
>>> http://git.zx2c4
It doesn't make any sense to symlink this unit file into /etc when the
unit file itself isn't even installed, with --disable-networkd. This
moves the GENERAL_ALIASES logic into the right "if" block.
---
Makefile.am | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Makefile.am
On Fri, Feb 21, 2014 at 4:19 PM, Lennart Poettering
wrote:
>
> Well, ultimately it's up the distributions to decide what they want to
> enable and what not.
True, but this requires manual patching and fixing up of `make
install`, which is a bummer.
> I think networkd is a good choice, especially
On Fri, Feb 21, 2014 at 3:27 PM, Samuli Suominen wrote:
> By passing --rootprefix= you can get systemd-udevd installed to
> /lib/systemd, as opposed to /usr/lib/systemd
> And by logic, network configuration is needed to accompany the daemon
> since /usr might not be mounted yet,
> the network conf
On Fri, 21.02.14 15:54, Łukasz Stelmach (l.stelm...@samsung.com) wrote:
> Fix problems with unresolved symbols when building on Ubuntu 12.04 x86_64.
>
> --8<---cut here---start->8---
> ./.libs/libudev.so: undefined reference to `__res_search'
> ./.libs/libudev.
On Fri, 21.02.14 15:03, Jason A. Donenfeld (ja...@zx2c4.com) wrote:
>
> On Fri, Feb 21, 2014 at 2:08 PM, Tom Gundersen wrote:
> > I'll just apply this patch and
> > add the /etc symlink in a follow-up.
>
> I appreciate merging my patch, so now administrators can disable it in
> a sane way (with
This reverts commit ca1a3847695d02ebe62007d8f335f23d3fe04638.
It's not right to install this by default. networkd is extremely new,
has no real world miles, and most importantly, simply
does-not-do-anything-at-all unless you write configuration files for it.
So, for folks who want to use networkd,
Fix problems with unresolved symbols when building on Ubuntu 12.04 x86_64.
--8<---cut here---start->8---
./.libs/libudev.so: undefined reference to `__res_search'
./.libs/libudev.so: undefined reference to `__res_query'
collect2: ld returned 1 exit status
--8<--
By passing --rootprefix= you can get systemd-udevd installed to
/lib/systemd, as opposed to /usr/lib/systemd
And by logic, network configuration is needed to accompany the daemon
since /usr might not be mounted yet,
the network configuration needs to go to same prefix with the systemd-udevd
Curren
On Fri, Feb 21, 2014 at 03:21:21PM +0100, Jason A. Donenfeld wrote:
> ---
> configure.ac | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/configure.ac b/configure.ac
> index 80c1449..8943c96 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -1150,6 +1150,7 @@ AC_MSG_RESULT([
>
---
configure.ac | 1 +
1 file changed, 1 insertion(+)
diff --git a/configure.ac b/configure.ac
index 80c1449..8943c96 100644
--- a/configure.ac
+++ b/configure.ac
@@ -1150,6 +1150,7 @@ AC_MSG_RESULT([
hostnamed: ${have_hostnamed}
timedated: ${have_ti
On Fri, Feb 21, 2014 at 2:08 PM, Tom Gundersen wrote:
> I'll just apply this patch and
> add the /etc symlink in a follow-up.
I appreciate merging my patch, so now administrators can disable it in
a sane way (without having to use mask). But still, why enable it by
default? I thought the idea of
On Fri, Feb 21, 2014 at 02:24:58PM +0100, Tom Gundersen wrote:
> On Fri, Feb 21, 2014 at 3:29 AM, Jason A. Donenfeld wrote:
> > Hey guys,
> >
> > This commit caught me by surprise:
> >
> > http://git.zx2c4.com/systemd/commit/?id=daeb71a36a98834664e4d95773a3629b746f4db8
> >
> > It wasn't in the
Previously we put the boot offset and boot ID into the completion, now
we use something similar to the coredumpctl completion, but only with
the boot offsets.
---
This is just something I'm working on, but would like some input. I'm fine
with it not having the boot ID's output, but that may be una
On Fri, Feb 21, 2014 at 3:29 AM, Jason A. Donenfeld wrote:
> Hey guys,
>
> This commit caught me by surprise:
>
> http://git.zx2c4.com/systemd/commit/?id=daeb71a36a98834664e4d95773a3629b746f4db8
>
> It wasn't in the NEWS or the mailing list post for 209, so when
> updating I encountered a bit
On Fri, 21.02.14 11:20, Thomas Bächler (tho...@archlinux.org) wrote:
> There was a copy-paste error introduced in commit
> c2ba3ad6604ef2e189d7e0a36d696e84d3ab
> which causes the following error when using timer units:
>
> Assertion '(x->type == SOURCE_MONOTONIC && y->type == SOURCE_MONOTONI
On Fri, Feb 21, 2014 at 1:53 PM, Lennart Poettering
wrote:
> On Fri, 21.02.14 04:38, Jason A. Donenfeld (ja...@zx2c4.com) wrote:
>
>> systemd-network.service should not be started unless the administrator
>> runs "systemctl enable systemd-network.service", as it's entirely
>> unessential and most
On Fri, 21.02.14 09:39, Michael Scherer (m...@zarb.org) wrote:
> > Applied! I made some changes though, there were some missing
> > bits to make sure the config hookup works correctly. I don't have any
> > apparmor available though. Could you check if everything works
> > correctly?
>
> I will, I
On Fri, 21.02.14 08:28, Holger Schurig (holgerschu...@gmail.com) wrote:
>
> Compilation works okay here. And "make check" said "PASS: test-namespace".
>
> > The change I made is to complain if __NR_setns is not defined.
>
> The approach with an error message (at runtime) was taken from
> iprout
On Fri, 21.02.14 04:38, Jason A. Donenfeld (ja...@zx2c4.com) wrote:
> systemd-network.service should not be started unless the administrator
> runs "systemctl enable systemd-network.service", as it's entirely
> unessential and most distributions use their own network management
> daemons instead.
On 21 Feb 2014 03:22, "Lennart Poettering" wrote:
>
> On Thu, 20.02.14 21:04, Umut Tezduyar Lindskog (umut.tezdu...@axis.com)
wrote:
>
> Tom commited this. Thanks!
>
> Tom, please always do a quick reply on the ML so that it is easy to see
> what is commited and what is not!
Sorry about that. It
Both systemd-analyze and systemd-run only access org.freedesktop.systemd1
on the bus. This patch allows using systemd-run --user and systemd-analyze
--user even if the user session's bus is not properly integrated with the
systemd user unit.
---
src/analyze/analyze.c | 2 +-
src/run/run.c
There was a copy-paste error introduced in commit
c2ba3ad6604ef2e189d7e0a36d696e84d3ab
which causes the following error when using timer units:
Assertion '(x->type == SOURCE_MONOTONIC && y->type == SOURCE_MONOTONIC) ||
(x->type == SOURCE_REALTIME && y->type == SOURCE_REALTIME)'
failed at src
I agree with Harald.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Am 20.02.2014 17:33, schrieb Dave Reisner:
> Hi all,
>
> I'm working on packaging the systemd 209 release, and I expect to have
> pkgrel=1 into [testing] in a few hours, barring any unforseen problems.
> It's a huge release (nearly 2000 commits since 208), and I don't
> anticipate that this will m
Hi,
Michael Scherer wrote (21 Feb 2014 08:39:12 GMT) :
> Le vendredi 21 février 2014 à 03:48 +0100, Lennart Poettering a écrit :
>> I don't have any apparmor available though. Could you check if
>> everything works correctly?
> I will, I do have a opensuse VM for that, and I think intrigeri in CC
Am 21.02.2014 04:41, schrieb Zbigniew Jędrzejewski-Szmek:
> On Fri, Feb 21, 2014 at 04:00:10AM +0100, Jason A. Donenfeld wrote:
>> systemd-networkd seems to get started by default in 209. Why is this?
>> What if I don't want to use it to manage my networks? Why does it have
>> to be on by default
Le vendredi 21 février 2014 à 03:48 +0100, Lennart Poettering a écrit :
> On Thu, 20.02.14 16:19, m...@zarb.org (m...@zarb.org) wrote:
>
> > From: Michael Scherer
> >
> > This permit to switch to a specific apparmor profile when starting a
> > daemon. This
> > will result in a non operation if
63 matches
Mail list logo
