Hello!
After upgrading my main test worker to a recent distribution, the UBI
test suite [0] fails at various places with -EBUSY.
The reason is that these tests create and remove UBI volumes rapidly.
A typical test sequence is as follows:
1. creation of /dev/ubi0_0
2. some exclusive operation, such
On Sun, Nov 26, 2023 at 10:36 PM Mantas Mikulėnas wrote:
>
> If I remember correctly, udev (recent versions) takes a BSD lock using
> flock(2) while processing the device, and tools are supposed to do the same.
> The flock() call can be set to wait until the lock can be taken.
Hmm, indeed. But
On Mon, Nov 27, 2023 at 9:29 AM Lennart Poettering
wrote:
> On So, 26.11.23 00:39, Richard Weinberger (richard.weinber...@gmail.com)
> wrote:
>
> > Hello!
> >
> > After upgrading my main test worker to a recent distribution, the UBI
> > test suite [0] fails at va
On Mon, Nov 27, 2023 at 9:29 AM Lennart Poettering
wrote:
> If they conceptually should be considered block device equivalents, we
> might want to extend the udev logic to such UBI devices too. Patches
> welcome.
Why doesn't udev flock() every device it is probing?
Or asked differently, why is t
On Wed, Nov 29, 2023 at 9:48 AM Lennart Poettering
wrote:
> > Why doesn't udev flock() every device it is probing?
> > Or asked differently, why is this feature opt-in instead of opt-out?
>
> Some software really doesn't like it if we take BSD locks on their
> devices, hence we don't take it blank
Hi!
Recent systemd-nspawn seems to support unprivileged containers (user
namespaces). That's awesome, thank you guys for working on that!
Maybe you can help me so sort this out, can I run any systemd enabled
distribution
using the most current systemd-nspawn?
Say, my host is FC22 using systemd-ns
Lennart,
Am 11.06.2015 um 12:08 schrieb Lennart Poettering:
> On Thu, 11.06.15 09:40, Richard Weinberger (richard.weinber...@gmail.com)
> wrote:
>
>> Hi!
>>
>> Recent systemd-nspawn seems to support unprivileged containers (user
>> namespaces). That's aweso
On Sun, Nov 8, 2015 at 1:17 PM, arnaud gaboury wrote:
> I am trying to understand how kernel modules are "passed" to nspawn container.
A container must not load any module as the kernel is a shared resource.
--
Thanks,
//richard
___
systemd-devel mail
Hi all,
after reading on the removal of kdbus from Rawhide[1] I've searched
the mailinglist archives for more details but didn't find anything.
So, what are your plans?
[1] https://lists.fedoraproject.org/pipermail/kernel/2015-October/006011.html
--
Thanks,
//richard
___
On Sun, Nov 8, 2015 at 10:35 PM, Greg KH wrote:
> On Sun, Nov 08, 2015 at 10:06:31PM +0100, Richard Weinberger wrote:
>> Hi all,
>>
>> after reading on the removal of kdbus from Rawhide[1] I've searched
>> the mailinglist archives for more details but didn'
On Mon, Nov 9, 2015 at 12:30 AM, Greg KH wrote:
> On Sun, Nov 08, 2015 at 10:39:43PM +0100, Richard Weinberger wrote:
>> On Sun, Nov 8, 2015 at 10:35 PM, Greg KH wrote:
>> > On Sun, Nov 08, 2015 at 10:06:31PM +0100, Richard Weinberger wrote:
>> >> Hi all,
>> &
->age_set in the IGNORE_DIRECTORY_PATH logic.
Signed-off-by: Richard Weinberger
---
src/tmpfiles/tmpfiles.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/tmpfiles/tmpfiles.c b/src/tmpfiles/tmpfiles.c
index 79fd0b7..c8d4abb 100644
--- a/src/tmpfiles/tmpfiles.c
+++ b/src/tmpfi
Am 27.08.2014 14:55, schrieb Richard Weinberger:
> If one has a config like:
> d /tmp 1777 root root -
> X /tmp/important_mount
>
> All files below /tmp/important_mount will be deleted as the
> /tmp/important_mount item will spuriously inherit a max age of 0
> from /tmp.
>
If one has a config like:
d /tmp 1777 root root -
X /tmp/important_mount
All files below /tmp/important_mount will be deleted as the
/tmp/important_mount item will spuriously inherit a max age of 0
from /tmp.
/tmp has a max age of 0 but age_set is (of course) false.
This affects also the PrivateT
On Tue, Sep 16, 2014 at 5:31 PM, Thomas Meyer wrote:
> Hi,
>
> I wrote a small patch for user-mode linux to register with machined by
> calling "CreateMachine". Is this a good idea to do so?
>
> I think machined gives you a nice overview over all running UML
> instances, also you get the scope uni
On Wed, Sep 17, 2014 at 1:09 AM, Zbigniew Jędrzejewski-Szmek
wrote:
> On Tue, Sep 16, 2014 at 05:31:05PM +0200, Thomas Meyer wrote:
>> Hi,
>>
>> I wrote a small patch for user-mode linux to register with machined by
>> calling "CreateMachine". Is this a good idea to do so?
> Yes, this sounds usefu
Am 09.09.2014 11:09, schrieb Richard Weinberger:
> If one has a config like:
> d /tmp 1777 root root -
> X /tmp/important_mount
>
> All files below /tmp/important_mount will be deleted as the
> /tmp/important_mount item will spuriously inherit a max age of 0
> from /tmp.
>
On Mon, Sep 29, 2014 at 8:29 PM, Thomas Meyer wrote:
> Hi,
>
> I get a timeout in the Fedora 21 alpha:
>
> [ TIME ] Timed out waiting for device
> dev-disk-by\x2duuid-008af19d\x2d2562\x2d49bd\x2d8907\x2d721ea08f3e14.device.
>
> But all devices are available from early kernel start:
> # ls -l /dev
Lennart,
Am 10.10.2014 um 18:44 schrieb Lennart Poettering:
> It's a bit more complex. While UML, qemu, kvm, currently don't, LXC,
> systemd-nspawn and libvirt-lxc all do talk directly to machined. (Note
> that LXC and libvirt-lxc are separate codebases, the latter is *not* a
> wrapper around the
Dear systemd and container folks,
at Plumbers the question raised how to provide cgroups to a systemd that lives
in a container (with user namespaces).
Due to the GDL train strikes I had to leave very soon and had no chance to
talk to you in person.
Was a solution proposed?
All I want to know is
...fixing LXC devel mailinglist... :-\
On Fri, Oct 17, 2014 at 11:35 PM, Richard Weinberger
wrote:
> Dear systemd and container folks,
>
> at Plumbers the question raised how to provide cgroups to a systemd that lives
> in a container (with user namespaces).
> Due to the GDL trai
Am 20.10.2014 um 18:24 schrieb Lennart Poettering:
> On Fri, 17.10.14 23:35, Richard Weinberger (richard.weinber...@gmail.com)
> wrote:
>
>> Dear systemd and container folks,
>>
>> at Plumbers the question raised how to provide cgroups to a systemd that
>> l
Am 20.10.2014 um 18:51 schrieb Lennart Poettering:
> On Mon, 20.10.14 18:49, Richard Weinberger (rich...@nod.at) wrote:
>
>> Am 20.10.2014 um 18:24 schrieb Lennart Poettering:
>>> On Fri, 17.10.14 23:35, Richard Weinberger (richard.weinber...@gmail.com)
>>> wr
Am 20.10.2014 um 19:04 schrieb Lennart Poettering:
> On Mon, 20.10.14 18:55, Richard Weinberger (rich...@nod.at) wrote:
>
>> Am 20.10.2014 um 18:51 schrieb Lennart Poettering:
>>> On Mon, 20.10.14 18:49, Richard Weinberger (rich...@nod.at) wrote:
>>>
>>>&
Am 20.10.2014 um 19:27 schrieb Lennart Poettering:
> On Mon, 20.10.14 19:16, Richard Weinberger (rich...@nod.at) wrote:
>
>>> Have you read the link I posted?
>>
>> Sure, I've also been in the room in Düsseldorf while you've read it
>> in front o
Hi!
I run a Linux container setup with openSUSE 13.1/2 as guest distro.
After some time containers slow down.
An investigation showed that the containers slow down because a lot of stale
user sessions slow down almost all systemd tools, mostly systemctl.
loginctl reports many thousand sessions.
Al
Am 26.11.2014 um 22:29 schrieb Richard Weinberger:
> Hi!
>
> I run a Linux container setup with openSUSE 13.1/2 as guest distro.
> After some time containers slow down.
> An investigation showed that the containers slow down because a lot of stale
> user sessions slow down
Am 28.11.2014 um 06:33 schrieb Martin Pitt:
> Hello all,
>
> Cameron Norman [2014-11-27 12:26 -0800]:
>> On Wed, Nov 26, 2014 at 1:29 PM, Richard Weinberger wrote:
>>> Hi!
>>>
>>> I run a Linux container setup with openSUSE 13.1/2 as guest distro.
>&g
Am 01.12.2014 um 01:18 schrieb Dave Chinner:
> On Sun, Nov 30, 2014 at 10:08:01PM +0100, Richard Weinberger wrote:
>> Am 30.11.2014 um 21:54 schrieb Dave Chinner:
>>> On Wed, Nov 26, 2014 at 12:36:52AM +0100, Richard Weinberger wrote:
>>>> systemd has a hard depende
At least LXC does not allow the container root to change
the OOM Score adjust value.
Signed-off-by: Richard Weinberger
---
Hi!
Within Linux containers we cannot use OOMScoreAdjust nor CapabilityBoundingSet
(and maybe
more related settings).
This patch tells systemd to ignore OOMScoreAdjust if
Am 09.04.2014 19:19, schrieb Tom Gundersen:
> On Mon, Apr 7, 2014 at 9:47 PM, Richard Weinberger wrote:
>> At least LXC does not allow the container root to change
>> the OOM Score adjust value.
>>
>> Signed-off-by: Richard Weinberger
>> ---
>> Hi!
>
Am 09.04.2014 20:28, schrieb Tom Gundersen:
> On Wed, Apr 9, 2014 at 7:39 PM, Richard Weinberger wrote:
>> Am 09.04.2014 19:19, schrieb Tom Gundersen:
>>> On Mon, Apr 7, 2014 at 9:47 PM, Richard Weinberger wrote:
>>>> At least LXC does not allow the container roo
Hi!
As of my understanding of systemd, device units depend hard udev.
Units like network@.service contain lines like
"BindsTo=sys-subsystem-net-devices-%i.device"
Within a Linux container this is a problem because there is no udev.
There systemd never receives an event for this device and the dev
Hi!
We're heavily using Linux containers in our production environment.
As modern Linux distributions move forward to systemd have to make sure that
systemd works within our containers.
Sadly we're facing issues with cgroups.
Our testbed consists of openSUSE 13.1 with Linux 3.13.1 and libvirt 1.2
On Thu, Feb 6, 2014 at 1:08 AM, Kay Sievers wrote:
> On Thu, Feb 6, 2014 at 12:56 AM, Lennart Poettering
> wrote:
>> On Wed, 05.02.14 23:44, Richard Weinberger (richard.weinber...@gmail.com)
>> wrote:
>
>>> We're heavily using Linux containers in our producti
35 matches
Mail list logo
