Re: [systemd-devel] "StandardOutput=console" don't work as expected

Hi, On Wed, Dec 30, 2015 at 2:52 AM, Michael Chapman wrote: > On Wed, 30 Dec 2015, Reindl Harald wrote: >>> > i am asking for StandardOutput=console get piped to the terminal >>> > systemctl was called - the rest is done by crond as all the years >>> > before >>> >>>

Re: [systemd-devel] systemd 219 fails to create and/or use loop devices (or any other device)

Hi, On Thu, Nov 19, 2015 at 7:42 AM, von Thadden, Joachim, SEVEN PRINCIPLES wrote: > using systemd 219-25 on Fedora 22 on a freshly created container I can not > make any > device. Usage of --capability=CAP_MKNOD makes no difference. > > Steps to reproduce: >

Re: [systemd-devel] at replacement

Hi, On Thu, Jul 12, 2018 at 12:04 PM Matt Zagrabelny wrote: > I know systemd can replace cron. Do folks use it to replace "at", too? > > I know it *can* - with two files per "at" entry and then enabling and > starting the timer. > > Is there an easier with to replace "at" with systemd than

Re: [systemd-devel] at replacement

On Thu, Jul 12, 2018 at 2:06 PM Matt Zagrabelny wrote: > On Thu, Jul 12, 2018 at 3:07 PM, Filipe Brandenburger > wrote: >> Take a look at systemd-run and, in particular, options such as >> --on-active=, --on-calendar= and --timer-property=, which allow you to >> set a

Re: [systemd-devel] When is a unit "loaded"?

Hey Daniel! On Wed, Jul 11, 2018 at 5:16 PM Daniel Wang wrote: > I have a unit, say foo.service, on my system that's in > /usr/lib/systemd/system, but disabled by preset. Not that it matters, but presets don't really matter here. The unit is disabled, period. > On system boot, it doesn't show

Re: [systemd-devel] Apparmor in containers

Hi, Actually, it seems AppArmor has support for containers and can have a specific profile for inside the containers only. Docker does support it: https://docs.docker.com/engine/security/apparmor/ Agree it shouldn't be too hard to hook this into nspawn... I don't really use AppArmor or know it

Re: [systemd-devel] how to login into a container booting with a minimal 'debian distro unstable' via nspawn

Hi Florian, On Sun, Mar 25, 2018 at 9:36 AM, Florian Held wrote: > how is it possible to log in into a container booting a minimal unstable > debian distro via nspawn. After running: > > # debootstrap --arch=amd64 unstable ~/debian-tree/ > # systemd-nspawn -bD

[systemd-devel] Filtering logs of a single execution of a (transient) service

Hi! So I'm testing a program repeatedly and using `systemd-run` to start a service with it, passing it a specific unit name. When the test finishes and I bring down the service, I want to be able to collect the journald logs for that execution of the test alone. Right now what I'm doing is

[systemd-devel] Cleanest way to halt a VM after a service has stopped

Hi, I found it's possible to halt a VM after a service has stopped by using something like this: ExecStopPost=/sbin/halt -p Is this the cleanest approach? Or would anyone have a better recommendation (perhaps using systemd-halt.service or similar)? Thanks! Filipe smime.p7s Description:

Re: [systemd-devel] At wits end... need to execute a script prior to anything getting killed/changed on reboot/shutdown

If you want to run it early in the shutdown process, then keep DefaultDependencies=yes, in which case it will run before the base dependencies start to get stopped. If you need some other resources to be up, for instance network, then add After=network.target, etc. Remember that when shutting

Re: [systemd-devel] Bugfix release(s)

So I think all the bits already exist somewhere and perhaps a small change in naming would go a long way to make these pushes smoother. If when we cut v240 from the master branch, we had called it v240-rc1 instead, perhaps it was clear that it could take some more testing before it was made

[systemd-devel] sd-boot on Fedora 30?

Hi, I've been trying to get sd-boot to work on Fedora 30, made some progress but not fully there yet... First I found my partition GPT type in /boot was incorrect and bootctl was trying to use /boot/efi instead. Ok, that fixed, now I get a list of kernels. But whenever I boot, I only get the

Re: [systemd-devel] Delegate= on slice before v237

Hey Lennart, Thanks for the clarification. On Tue, Feb 12, 2019 at 2:17 AM Lennart Poettering wrote: > On Mo, 11.02.19 16:39, Filipe Brandenburger (filbran...@google.com) wrote: > > Before systemd v237 (when Delegate= was no longer allowed on slice > > units)... Did setti

<    1   2