Le 04/03/2015 16:27, Michael Biebl a écrit :
2015-03-04 15:41 GMT+01:00 Lennart Poettering :
Well, just removing the symlink is kinda pointless. It might still be pulled
in by anything else that implicitly depepends on /tmp.
What unit is supposed to pull in tmp.mount explicitly? If a generic
un
I have a need to put my NICs in "RAID0" so to speak, but according to
materials I have found on net I can't use NIC bonding driver because I
would need LACP (IEEE whatever) aware L2 switch, so I was refered to
teaming driver, which should be ( if those folks is to be believed)
replacing bond dr
> Alternatively, if you're attached to the name bond0, you might be able
> to something like this (not tested with systemd-networkd):
>
> /etc/modprobe.d/rename-bond.conf:
>
> install bonding /usr/sbin/modprobe --ignore-install bonding \
> $CMDLINE_OPTS; /usr/sbin/ip link set dev bond0 down
> The logic here is that when we create a new bond we will create it
> with these settings, but we will not change the settings of a
> preexisting bond, as that may have been created by somebody else we
> don't know about so we figure better leave it alone.
>
> The confusing part here is that the
On Tue, Mar 03, 2015 at 05:18:00PM +, Jay Faulkner wrote:
>
> On Mar 3, 2015, at 8:55 AM, Topi Miettinen
> mailto:toiwo...@gmail.com>> wrote:
>
> On 03/03/15 01:28, Jay Faulkner wrote:
> Hey,
>
> Lennart reviewed this in IRC and suggested I refactor the change in this
> manner. Now, we have
Oh wait, I c, yes I had same question.
On Wed, Mar 4, 2015 at 8:07 PM, Shawn Landden wrote:
> On Wed, Mar 4, 2015 at 7:58 PM, Zbigniew Jędrzejewski-Szmek <
> zbys...@in.waw.pl> wrote:
>
>> On Tue, Mar 03, 2015 at 04:21:30PM -0800, Shawn Landden wrote:
>> > also switch to
>> > ---
>> > src/udev
On Wed, Mar 4, 2015 at 7:58 PM, Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:
> On Tue, Mar 03, 2015 at 04:21:30PM -0800, Shawn Landden wrote:
> > also switch to
> > ---
> > src/udev/udev-builtin-usb_id.c | 35 ++-
> > 1 file changed, 18 insertions(+), 1
On Tue, Mar 03, 2015 at 04:21:30PM -0800, Shawn Landden wrote:
> also switch to
> ---
> src/udev/udev-builtin-usb_id.c | 35 ++-
> 1 file changed, 18 insertions(+), 17 deletions(-)
>
> diff --git a/src/udev/udev-builtin-usb_id.c b/src/udev/udev-builtin-usb_id.c
>
On Wed, Mar 04, 2015 at 04:32:17PM +0100, Hannes Reinecke wrote:
> On large system we hit the limit on 512 simultaneous dbus
> connections, resulting in tons of annoying messages:
>
> Too many concurrent connections, refusing
>
> This patch raises the limit to 4096.
>
> Signed-off-by: Hannes Rei
On Wed, Mar 04, 2015 at 04:32:16PM +0100, Hannes Reinecke wrote:
> Currently the code will silently blank out events
> if there are more then 512 epoll events, causing them
> never to be handled at all.
> This patch removes the cap on the number of events
> for epoll_wait, thereby avoiding this iss
On Thu, Mar 05, 2015 at 01:22:01AM +0100, Mirco Tischler wrote:
> Using the DIR macro breaks caching and has no benefit as it only offers
> performance improvements when AS_FOR is used with a single element list.
> Also --with-lds-dir= was broken as we never set have_efi_lds in this case.
> Fix thi
On Wed, Mar 04, 2015 at 06:43:20PM -0500, Zachary Cook wrote:
> ---
> man/systemd-cryptsetup-generator.xml| 6 ++
> man/systemd-debug-generator.xml | 6 ++
> man/systemd-efi-boot-generator.xml | 4 +---
> man/systemd-fstab-generator.xml | 6 ++
> man/systemd-ge
On Wed, Mar 04, 2015 at 03:15:02PM -0800, Shawn Landden wrote:
> Fix handling of abstract unix domain sockets too.
Please split it into two patches.
> ---
> TODO | 2 --
> man/systemd.socket.xml | 5 -
> src/core/service.c | 24
> src/sha
2015-03-05 1:22 GMT+01:00 Mirco Tischler :
> Thanks
> Mirco
>
Sorry I messed up, this was supposed to be.
I figured it out. Patch in seperate Mail
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/lis
Thanks
Mirco
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Using the DIR macro breaks caching and has no benefit as it only offers
performance improvements when AS_FOR is used with a single element list.
Also --with-lds-dir= was broken as we never set have_efi_lds in this case.
Fix this and check if PATH actually contains the efi-lds file.
---
configure.a
---
man/systemd-cryptsetup-generator.xml| 6 ++
man/systemd-debug-generator.xml | 6 ++
man/systemd-efi-boot-generator.xml | 4 +---
man/systemd-fstab-generator.xml | 6 ++
man/systemd-getty-generator.xml | 5 ++---
man/systemd-gpt-auto-generator.xml
Fix handling of abstract unix domain sockets too.
v2
---
TODO | 2 --
man/systemd.socket.xml | 5 -
src/core/service.c | 24
src/shared/socket-util.c | 25 +++--
4 files changed, 47 insertions(+), 9 deletions(-)
diff
Fix handling of abstract unix domain sockets too.
---
TODO | 2 --
man/systemd.socket.xml | 5 -
src/core/service.c | 24
src/shared/socket-util.c | 25 +++--
4 files changed, 47 insertions(+), 9 deletions(-)
diff --gi
On Wed, 04.03.15 18:51, Alexander Larsson (al...@redhat.com) wrote:
> If i run a transient scope on the user systemd instance like:
>
> $ systemd-run --user --scope true
>
> Then the scope seems to live past the end of the process. Is there any
> way to make it automatically go away with the las
On Wed, 04.03.15 18:50, Alexander Larsson (al...@redhat.com) wrote:
> The user instance of systemd does not seem to apply the DevicePolicy for
> scopes. I.e. I can run:
None of the controllers are currently available to unprivileged
processes. This will be opened up as the kernel gets improved to
dennis.mur...@wipro.com schrieb:
>> nilfs_cleanerd is invoked through /sbin/mount.nilfs2 helper. [2] The
>> helper is called from /sbin/mount if it exists.
>
> What is confusing to me, is an umount then a mount will start the
> nilfs_cleanerd process so it does exist on the system. I had expect
If i run a transient scope on the user systemd instance like:
$ systemd-run --user --scope true
Then the scope seems to live past the end of the process. Is there any
way to make it automatically go away with the last process in the
cgroup?
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
The user instance of systemd does not seem to apply the DevicePolicy for
scopes. I.e. I can run:
$ systemd-run --user --scope --property=DevicePolicy=strict glxgears
Running as unit run-994.scope.
... runs fine, should fail to use DRI ...
$ cat /run/user/1000/systemd/user/run-994.scope.d/50-Device
On 03/04/2015 03:43 AM, Tom Gundersen wrote:
The logic here is that when we create a new bond we will create it
with these settings, but we will not change the settings of a
preexisting bond, as that may have been created by somebody else we
don't know about so we figure better leave it alone.
T
Currently the code will silently blank out events
if there are more then 512 epoll events, causing them
never to be handled at all.
This patch removes the cap on the number of events
for epoll_wait, thereby avoiding this issue.
Signed-off-by: Hannes Reinecke
---
src/libsystemd/sd-event/sd-event.
On large system we hit the limit on 512 simultaneous dbus
connections, resulting in tons of annoying messages:
Too many concurrent connections, refusing
This patch raises the limit to 4096.
Signed-off-by: Hannes Reinecke
---
src/core/dbus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On large machines we hit the limit on 512 concurrent dbus connections
pretty easily, so we're greeted with tons of messages
Too many concurrent connections, refusing
To raise this limit, however, there another cap on the number of
accepted epoll events, which is particularly nasty as it will
just
On large system we hit the limit on 512 simultaneous dbus
connections, resulting in tons of annoying messages:
Too many concurrent connections, refusing
This patch raises the limit to 4096.
Signed-off-by: Hannes Reinecke
---
src/core/dbus.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
2015-03-04 15:41 GMT+01:00 Lennart Poettering :
> Well, just removing the symlink is kinda pointless. It might still be pulled
> in by anything else that implicitly depepends on /tmp.
What unit is supposed to pull in tmp.mount explicitly? If a generic
unit did that, this sounds like a bug.
--
W
Currently the code will silently blank out events
if there are more then 512 epoll events, causing them
never to be handled at all.
This patch removes the cap on the number of events
for epoll_wait, thereby avoiding this issue.
Signed-off-by: Hannes Reinecke
---
src/libsystemd/sd-event/sd-event.
On large machines we hit the limit on 512 concurrent dbus connections
pretty easily, so we're greeted with tons of messages
Too many concurrent connections, refusing
To raise this limit, however, there another cap on the number of
accepted epoll events, which is particularly nasty as it will
just
With the help of grawity on irc, I assembled this small patch file for a
possible temporary workaround. Just hardcoded systemd-networkd to not
touch the can0 interface.
--- a/src/network/networkd-manager.c2015-02-11 17:30:31.800897770
+0100
+++ b/src/network/networkd-manager.c2015-03-0
On Wed, 04.03.15 15:25, Didier Roche (didro...@ubuntu.com) wrote:
> Le 04/03/2015 13:40, Lennart Poettering a écrit :
> >On Wed, 04.03.15 13:19, Didier Roche (didro...@ubuntu.com) wrote:
> >
> >>Le 04/03/2015 12:49, Lennart Poettering a écrit :
> >>>On Wed, 04.03.15 09:21, Didier Roche (didro...@u
Le 04/03/2015 13:40, Lennart Poettering a écrit :
On Wed, 04.03.15 13:19, Didier Roche (didro...@ubuntu.com) wrote:
Le 04/03/2015 12:49, Lennart Poettering a écrit :
On Wed, 04.03.15 09:21, Didier Roche (didro...@ubuntu.com) wrote:
Hey,
It seems that we discovered an issue if a service decl
On Wed, 2015-03-04 at 12:52 +0100, Lennart Poettering wrote:
> On Tue, 03.03.15 21:06, Thomas Haller (thal...@redhat.com) wrote:
>
> > sd_dhcp6_client_new() tried to set the DUID based on the machine id.
> > If the host has no /etc/machine-id, the constructor would fail
> > making it impossible to
On Wed, 04.03.15 13:19, Didier Roche (didro...@ubuntu.com) wrote:
> Le 04/03/2015 12:49, Lennart Poettering a écrit :
> >On Wed, 04.03.15 09:21, Didier Roche (didro...@ubuntu.com) wrote:
> >
> >>Hey,
> >>
> >>It seems that we discovered an issue if a service declares some relationship
> >>with a .
Le 04/03/2015 12:49, Lennart Poettering a écrit :
On Wed, 04.03.15 09:21, Didier Roche (didro...@ubuntu.com) wrote:
Hey,
It seems that we discovered an issue if a service declares some relationship
with a .mount unit.
For instance, having tmp.mount disable (and nothing mounting /tmp as tmpfs
i
On Tue, 03.03.15 21:06, Thomas Haller (thal...@redhat.com) wrote:
> sd_dhcp6_client_new() tried to set the DUID based on the machine id.
> If the host has no /etc/machine-id, the constructor would fail
> making it impossible to create an sd_dhcp6_client instance.
We do not even allow bootups with
On Wed, 04.03.15 09:21, Didier Roche (didro...@ubuntu.com) wrote:
> Hey,
>
> It seems that we discovered an issue if a service declares some relationship
> with a .mount unit.
> For instance, having tmp.mount disable (and nothing mounting /tmp as tmpfs
> in fstab):
tmp.mount is enabled staticall
Nicely done. Applied.
Though, I must say that a missing /etc/machine-id sounds like a pretty
serious problem, so not sure adding workarounds for that makes sense
(but that's anyway not part of this patch).
Cheers,
Tom
On Tue, Mar 3, 2015 at 9:06 PM, Thomas Haller wrote:
> sd_dhcp6_client_new()
On Thu, Feb 26, 2015 at 7:31 PM, Jan Janssen wrote:
> Hi,
> since commit commit 5bac5235934fabe5a3e6a9d47f4812f81034c427, networkd
> cannot acquire DHCP leases on my router if I dual boot with windows.
>
> It seems to be that my router is borked since I do get leases after
> resetting it to factor
Great stuff! Applied.
Thanks!
Tom
On Tue, Mar 3, 2015 at 7:49 PM, Jan Janssen wrote:
> ---
> man/systemd.network.xml | 8
> src/network/networkd-dhcp4.c | 16
> src/network/networkd-network-gperf.gperf | 1 +
> src/network/networkd-netwo
Hi Mikhail,
On Sat, Feb 28, 2015 at 1:26 PM, Mikhail Morfikov wrote:
> I've just finished migration from /etc/init.d/networking script to
> systemd-networkd solution, and I just wanted to ask a couple of things.
>
> First, I have two interfaces -- one wire (eth1) and one wifi (wlan0),
> and I wan
I have an Atom NM10-based industrial PC with three e1000e devices and a
PEAK can device (PCI ID 001c:0008). After updating from 216 to 219,
systemd-networkd is unable to get my e1000e-devices up and running. I
don't have any configuration for can0 within /etc/systemd/network.
Two files in /etc
Le 04/03/2015 09:29, Andrei Borzenkov a écrit :
On Wed, Mar 4, 2015 at 11:21 AM, Didier Roche wrote:
tmpfs on /tmp type tmpfs (rw)
status on tmp.mount:
Loaded: loaded (/lib/systemd/system/tmp.mount; disabled; vendor preset:
enabled)
It says "enabled" here, although I'm not sure what "vend
On Wed, Mar 4, 2015 at 11:21 AM, Didier Roche wrote:
> Hey,
>
> It seems that we discovered an issue if a service declares some relationship
> with a .mount unit.
> For instance, having tmp.mount disable (and nothing mounting /tmp as tmpfs
> in fstab):
>
> foo.service:
> [Unit]
> After=tmp.mount
>
Just for the record: I didn't try on trunk yet, only systemd v219 that
we ship in vivid.
Cheers,
Didier
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Hey,
It seems that we discovered an issue if a service declares some
relationship with a .mount unit.
For instance, having tmp.mount disable (and nothing mounting /tmp as
tmpfs in fstab):
foo.service:
[Unit]
After=tmp.mount
[Service]
ExecStart=/bin/echo foo
[Install]
WantedBy=multi-user.tar
49 matches
Mail list logo
