Re: [systemd-devel] mount-on-demand for backups; hooks for indicating success/failure

On Thu, 09.03.17 15:53, Jonathan Dowland (jon+systemd-de...@alcopop.org) wrote: > Hey, > > I have some backup services which depend on mounts. I want those > filesystems unmounted when the backup jobs are not running. This is > easily achieved with StopWhenUnneeded. > > I also want to trigger

Re: [systemd-devel] Can a systemd --user instance rely on After= of systemd --system instance?

On Sat, 04.03.17 22:07, Andrei Borzenkov (arvidj...@gmail.com) wrote: > 04.03.2017 13:49, Peter Hoeg пишет: > > Hi, > > > >> If I have a user service which needs to have the system database server > >> available: How do I construct a proper depend? > > > > As Lennart was pointing out, the user

Re: [systemd-devel] udev - ignore/hide persistent storage

On Fri, 31.03.17 11:30, lejeczek (pelj...@yahoo.co.uk) wrote: > > > sorry guys to bother you, but > > > I'll see myself going slowly mad next week, for I've been reading and > > > tryingand trying.. > > > > > > and I fail to tell udev to ignore a device and not to create symlinks. > > > I need

Re: [systemd-devel] udev - ignore/hide persistent storage

On 31/03/17 08:00, Lennart Poettering wrote: On Thu, 30.03.17 21:40, lejeczek (pelj...@yahoo.co.uk) wrote: sorry guys to bother you, but I'll see myself going slowly mad next week, for I've been reading and tryingand trying.. and I fail to tell udev to ignore a device and not to create

Re: [systemd-devel] systemd reboot problem

Note that if you are calling from C code, you might want to call it through the Dbus API, rather than the "system" system call. As for debugging what blocks the shutdown, here are a few clues * does "systemctl reboot -f" stop the system correctly ? if yes, one of your daemons is blocking

Re: [systemd-devel] Renaming interfaces with systemd.link

On 03/30/2017 10:15 AM, Lennart Poettering wrote: My educated guess is that your .link file was ignored due to the existance of /usr/lib/systemd/network/99-default.link. Make sure to prefix your .link file with some number < 99 to ensure it takes precedence. I think I've asked this before, but

[systemd-devel] systemd mount point disappearing on underlying device loss?

In Centos7/systemd, a mount point goes away automatically if the underlying device is gone. In Centos6/Rhel6 (ie before systemd) and before, losing a underlying device would yield Input/Output error on accessing the mount point, and the mount point still remains in the system. Is there any way

Re: [systemd-devel] udev - ignore/hide persistent storage

On Thu, 30.03.17 21:40, lejeczek (pelj...@yahoo.co.uk) wrote: > sorry guys to bother you, but > I'll see myself going slowly mad next week, for I've been reading and > tryingand trying.. > > and I fail to tell udev to ignore a device and not to create symlinks. > I need someone to 100% confirm

Re: [systemd-devel] Temporarily stopping a service while oneshot is running

On Thu, 30.03.17 21:42, Kai Krakow (hurikha...@gmail.com) wrote: > Am Thu, 30 Mar 2017 16:13:25 +0200 > schrieb Lennart Poettering : > > > On Tue, 21.03.17 07:47, Ian Pilcher (arequip...@gmail.com) wrote: > > > > > I have a oneshot service (run from a timer) that updates

Re: [systemd-devel] systemd mount point disappearing on underlying device loss?

01.04.2017 00:05, Suresh Rajagopalan пишет: > In Centos7/systemd, a mount point goes away automatically if the underlying > device is gone. > > In Centos6/Rhel6 (ie before systemd) and before, losing a underlying device > would yield Input/Output error on accessing the mount point, and the mount >

Re: [systemd-devel] nspawn: how to allow containers to connect to a specific host's port and prevent all the rest ?

On Tue, 07.03.17 10:02, Fabien Meghazi (f...@odoo.com) wrote: > Hello everyone, > > I would like to constraint the network in the containers I spawn using > nspawn. > What I'd like to achieve is the following: > > - prevent the containers to use the network interfaces of the host > - make one