Re: [systemd-devel] [PATCH] Add handling for bind/unbind actions

2017-08-31 Thread systemd github import bot
Patchset imported to github. To create a pull request, one of the main developers has to initiate one via: -- Generated by https://github.com/haraldh/mail2git ___

[systemd-devel] [PATCH] Add handling for bind/unbind actions

2017-08-31 Thread Dmitry Torokhov
Newer kernels will emit uevents with "bind" and "unbind" actions. These uevents will be issued when driver is bound to or unbound from a device. "Bind" events are helpful when device requires a firmware to operate properly, and driver is unable to create a child device before firmware is properly l

[systemd-devel] RFE and DISCUSSION: Custom commands in systemd services

2017-08-31 Thread Introoter
Hello, As discussed in https://github.com/systemd/systemd/issues/6690, there's a need to add an option to the specific systemd services to be able to execute arbitrary actions in the context of that particular service (think service postgres initdb). Although, I do know that the current way to g

Re: [systemd-devel] Permission/updating problems; different behaviour of two identical nspawn containers

2017-08-31 Thread Lennart Poettering
On Mi, 30.08.17 17:24, Olaf the Lost Viking (olaf.the.lost.vik...@gmail.com) wrote: > Hi ML, > > > currently I am seeing differences between two, what I consider identical, > nspawn-containers which prevents me to update one of them. (Lots of) details > are at the end of the mail. > > I set

Re: [systemd-devel] Requirements for successful mounting of RootImage?

2017-08-31 Thread Lennart Poettering
On So, 20.08.17 13:20, Topi Miettinen (toiwo...@gmail.com) wrote: > >> The file /fs has a MBR partition table: > >> Disk /dev/loop0: 1.1 MiB, 1192960 bytes, 2330 sectors > >> Units: sectors of 1 * 512 = 512 bytes > >> Sector size (logical/physical): 512 bytes / 512 bytes > >> I/O size (minimum/opt

Re: [systemd-devel] Reliable way to finish system units before termination through systemd shutdown / reboot routines

2017-08-31 Thread Rick Beldin
On 08/31/2017 10:05 AM, Lennart Poettering wrote: > I have running some virtualbox instances under systemd control and use > vboxautostart-service > for starting and stopping (saving). This is running on Centos7 > As long as I use systemctl stop vboxautostart-service for termination, > everythi

Re: [systemd-devel] type=notify not working as intended

2017-08-31 Thread Lennart Poettering
On Di, 15.08.17 09:29, Kalpa Gunarathna (ka...@sigscale.com) wrote: > Hello all, > > I have scripted a service unit as follow. > > [Unit] > Description="A test service" > After=epmd.service epmd.socket > > [Service] > ExecStart=/home/otpuser/bin/start > Type=notify > NotifyAccess=all > WorkingD

Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

2017-08-31 Thread Lennart Poettering
On Di, 15.08.17 09:14, Sergei Franco (sergei.fra...@gmail.com) wrote: > Please accept my apologies for HTML email (using gmail client). > > For our organisation mid-2016 was the year of systemd, and exposure > has been minimal (only new builds), so I guess you had a head start. I > fully grasp th

Re: [systemd-devel] Is it possible to config rate limit for journal based on severity

2017-08-31 Thread Lennart Poettering
On Mi, 16.08.17 10:35, P.R.Dinesh (pr.din...@gmail.com) wrote: > With respect to Journal rate limit (RateLimitIntervalSec=, RateLimitBurst=) > I would like to rate limit more for low severity logs and less for high > severity logs. Is this feasible? also can we have different rate limit > configu

Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

2017-08-31 Thread Lennart Poettering
On Fr, 11.08.17 05:47, Zhujiafa (zhuji...@huawei.com) wrote: > add > " systemd.journald.forward_to_console=1 " > to your kernel parameters. Note that this causes log output to be dumped to the system console, and not the TTY you are actually invoking "systemctl" from, i.e. not any SSH tty or so

Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

2017-08-31 Thread Lennart Poettering
On Mo, 14.08.17 22:31, Sergei Franco (sergei.fra...@gmail.com) wrote: > Admins expect output when starting and stopping services. > This is even more important when there are runbooks and other processes > involved. > The journalctl output is very messy (because it is a log). When you are on > cal

Re: [systemd-devel] Reading an "ao" signature message with the sdbus c library?

2017-08-31 Thread Lennart Poettering
On Do, 17.08.17 13:43, James Johnson (jjjwallyh...@gmail.com) wrote: > Hello, > > Can someone please point me to the correct method for reading an "ao" > signature dbus message using the sd_bus C api? > > I am trying to read all the network devices with the following call: > > result = sd_bus

Re: [systemd-devel] systemd-logind fails to start

2017-08-31 Thread Lennart Poettering
On Mo, 14.08.17 10:09, Robin Becker (ro...@reportlab.com) wrote: > After a recent update I started having problems logging in. > > It seems systemd-logind is timing out for some reason. > > I see this in the journalctl -xe output > > > > > -- Unit systemd-logind.service has begun starting up

Re: [systemd-devel] Reliable way to finish system units before termination through systemd shutdown / reboot routines

2017-08-31 Thread Lennart Poettering
On Di, 15.08.17 14:25, Reiner Wenke (reiner.we...@nxp.com) wrote: > Hello, > > I have running some virtualbox instances under systemd control and use > vboxautostart-service > for starting and stopping (saving). This is running on Centos7 > As long as I use systemctl stop vboxautostart-service f