[systemd-devel] how to put max time limit on reboot time

Hi Currently it appears that systemd does not provide a way to put max time limit for system reboot. So there is no way to get system reboot within specified time limit even if hardware watchdog is present in system. Using RunTimeWatchDogSec,ShutDownTimeWatchDogSec and JobTimeoutSec,JobTimeoutAc

[systemd-devel] loginctl hangs when run at boot time

Hi, On the CentOS7 AWS with the following systemd installed: systemd-219-42.el7_4.4.x86_64 Any loginctl command that we try to run at boot time (during the AWS "user data" section of cloud-init), will hang and then timeout. The same loginctl command run after you ssh into the box and become

Re: [systemd-devel] journald fsync() errors

On Wed, Apr 04, 2018 at 04:49:29PM +0200, Lennart Poettering wrote: > On Di, 03.04.18 14:10, [email protected] ([email protected]) wrote: > > > Back when I worked on making fsync() in journald asynchronous, I > > preserved the existing strategy of ignoring fsync() errors. > > > > In reading [

Re: [systemd-devel] Socket activation (for GitWeb)?

On Wed, Apr 4, 2018, 22:18 Alex Ivanov wrote: > Hi. > I want to use systemd as fastcgi spawner for gitweb + nginx. > The traffic is low and number of users is limited + traversal bots. For > that reason I've decided to use following mimimal services > > gitweb.socket: > [Unit] > Description=GitWe

[systemd-devel] Socket activation (for GitWeb)?

Hi. I want to use systemd as fastcgi spawner for gitweb + nginx. The traffic is low and number of users is limited + traversal bots. For that reason I've decided to use following mimimal services gitweb.socket: [Unit] Description=GitWeb Socket [Socket] ListenStream=/run/gitweb.sock Accept=false

Re: [systemd-devel] journald fsync() errors

On Di, 03.04.18 14:10, [email protected] ([email protected]) wrote: > Back when I worked on making fsync() in journald asynchronous, I > preserved the existing strategy of ignoring fsync() errors. > > In reading [1], I am reminded of this situation and am again wondering > why this is the cas

Re: [systemd-devel] nspawn: how to rename network interfaces?

On Mi, 04.04.18 09:05, Mantas Mikulėnas ([email protected]) wrote: > > >> Hi there, > > >> I just tried to rename ipvlan and macvlan devices in a container with > > systemd.link. This does not seem to work with debian stretch (host and > > container). > > >> > > >> Is it possible to rename ipvla

Re: [systemd-devel] nspawn: how to rename network interfaces?

On Wed, Apr 4, 2018, 11:37 Matthias Pfau wrote: > > Apr 3, 2018, 9:56 PM by [email protected]: > > > On Tue, Apr 3, 2018, 21:42 Matthias Pfau <> [email protected] > > > wrote: > > > >> Hi there, > >> I just tried to rename ipvlan and macvlan devices in a container