On Mo, 04.07.22 23:15, Michael Biebl ([email protected]) wrote:
> Am Mo., 4. Juli 2022 um 19:36 Uhr schrieb Lennart Poettering
> :
> >
> > eOn So, 03.07.22 19:29, Uwe Geuder ([email protected])
> > wrote:
> >
> > > Hi!
> > >
> > > When I run the command given below on a current Fed
Am Mo., 4. Juli 2022 um 19:36 Uhr schrieb Lennart Poettering
:
>
> eOn So, 03.07.22 19:29, Uwe Geuder ([email protected]) wrote:
>
> > Hi!
> >
> > When I run the command given below on a current Fedora CoreOS system
> > (systemd 250 (v250.6-1.fc36)) I get a result I absolute cannot
eOn So, 03.07.22 19:29, Uwe Geuder ([email protected]) wrote:
> Hi!
>
> When I run the command given below on a current Fedora CoreOS system
> (systemd 250 (v250.6-1.fc36)) I get a result I absolute cannot understand.
> Can anybody help me with what is wrong there?
>
> $ systemd-ru
On Mo, 04.07.22 12:37, Harald Dunkel ([email protected]) wrote:
> Hi folks,
>
> systemctl status does a nice job showing LXC containers and their
> process trees, but I wonder if it could show memory and cpu limits,
> memory utilization, swap, etc as well, even if the LXC or docker or
> wha
> > I'd love pointers on how to get this working, or hear from people
> > who've tried anything similar.
Anyone else using Fedora Silverblue as a systemd dev machine?
Did you just layer the required packages? Is there a better way?
> You have to fix the kernel to properly virtualize block devices
On Do, 09.06.22 11:40, Lewis Gaul ([email protected]) wrote:
> Hi everyone,
>
> [Disclaimer: cross posting from
> https://github.com/containers/podman/discussions/14538]
>
> Apologies that this is more of a Linux cgroup question than specific to
> systemd, but I was wondering if someone here mi
Hi folks,
systemctl status does a nice job showing LXC containers and their
process trees, but I wonder if it could show memory and cpu limits,
memory utilization, swap, etc as well, even if the LXC or docker or
whatever container wasn't started by systemd? cgroup1 and unified,
if possible.
I wo
On So, 26.06.22 02:57, Léo ([email protected]) wrote:
> Hello,
>
> I would like to know the purpose of this assert operation:
> https://github.com/systemd/systemd/blob/v251/src/home/homed-home.c#L2697
>
> What does it mean if it fails?
It just encodes that this function expects to be called wit
On Mi, 15.06.22 07:31, Kevin P. Fleming ([email protected]) wrote:
> I've got a number of systems that use BIRD to learn the routes
> available on their networks, and as a result some services on those
> systems attempt to start up before the routes have been learned. If
> those services attempt to ma
On Di, 28.06.22 22:01, Ananth Bhaskararaman ([email protected]) wrote:
> Has anyone had success using mkosi to generate images inside a
> toolbox container? I'm running Fedora 36 Silverblue.
mkosi needs loopback block devices. They are not virtualized for
containers on Linux. That's a kernel issue
On Mo, 27.06.22 23:36, Lukasz Stelmach ([email protected]) wrote:
> Hi,
>
> I need an apparently exotic configuration and I don't know how to
> approach the problem. Here are the requirements:
>
> - [email protected] (systemd --user)
> + runs with Priv SMACK label (SmackProcessLabel in user
Hi!
When I run the command given below on a current Fedora CoreOS system
(systemd 250 (v250.6-1.fc36)) I get a result I absolute cannot understand.
Can anybody help me with what is wrong there?
$ systemd-run --user sh -c 'while true; do echo foo; df -h /var/log/journal/;
echo $?; sleep 3; done'
On Mo, 30.05.22 08:13, Ulrich Windl ([email protected]) wrote:
> Hi!
>
> Just in case: Does anybody have any idea what might be causing this
> effect (https://github.com/QubesOS/qubes-issues/issues/7335)?
LVM issues you have to ask the LVM people about really.
Lennart
--
Lennart
On Di, 31.05.22 02:48, Wang, Yuan1 ([email protected]) wrote:
> Hi
>
> Need your kind help for one question!
>
> Do libudev have a function that could be used to filter the message with
> property from kernel socket?
No, because that is not optimizable. i.e. we have no way to filter
these mis
14 matches
Mail list logo
