Re: [systemd-devel] systemd-notify

2019-04-18 Thread Felipe Sateler
ify > synchronous rather than fire-and-forget and expect it to wait for a > response from systemd. If the launch-xenstore script starts a daemon and then exists: why not make the unit Type=forking and thus forget about systemd-notify --ready ? -- Saludos, Felipe Sateler _

Re: [systemd-devel] /etc/systemd/system/default.target.wants/no longer checked for unit files

2017-07-14 Thread Felipe Sateler
hough: > https://codesearch.debian.net/search?q=WantedBy%3Ddefault.target > > If default.target is not supposed to be used, then this should be > mentioned somewhere. The user manager has a real default.target. Many (most?) of the units listed above are user services. -- Saludos, Felipe Sateler ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Github systemd issue 6237

2017-07-05 Thread Felipe Sateler
time with a non- ignorable EINVAL. This is different from things it defines itself, such as @ settings for SystemCallFilter. -- Saludos, Felipe Sateler ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Should automount units for network filesystems be Before=local-fs.target?

2017-04-28 Thread Felipe Sateler
On Thu, Apr 27, 2017 at 9:50 PM, Michael Chapman wrote: > On Fri, 28 Apr 2017, Felipe Sateler wrote: > >> On Thu, 27 Apr 2017 15:53:51 +1000, Michael Chapman wrote: >> >> Hello all, >>> >>> At present, when systemd-fstab-generator creates an automount u

Re: [systemd-devel] Should automount units for network filesystems be Before=local-fs.target?

2017-04-27 Thread Felipe Sateler
unt 5. boom Since the whole point of the exercise was to have some.service start earlier, and this implies that some.service will be stopped later, I deem this scenario likely if what you propose were implemented. -- Saludos, Felipe Sateler ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Factoring out initctl support

2016-04-27 Thread Felipe Sateler
On 27 April 2016 at 10:41, Daniel Mack wrote: > On 04/27/2016 12:29 AM, Felipe Sateler wrote: >> On Tue, 26 Apr 2016 17:28:34 +0200, Daniel Mack wrote: >> >>> Hi Michael, >>> >>> On 04/15/2016 11:00 PM, Daniel Mack wrote: >>>> On 04/15/2016

Re: [systemd-devel] Factoring out initctl support

2016-04-26 Thread Felipe Sateler
source would have to be somehow imported into the debian systemd source, and then used to build the shipped binary (ie, not importing the binary artifacts alone). -- Saludos, Felipe Sateler ___ systemd-devel mailing list systemd-devel@lists.freede

Re: [systemd-devel] Pulseaudio & systemd-nspawn

2015-11-02 Thread Felipe Sateler
e better option is to load the tcp pulseaudio module, allow connections from the container ip, and inject PULSE_SERVER envvar into the container. -- Saludos, Felipe Sateler ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] [HEADSUP] nspawn/networkd: moving from iptables to nftables

2015-10-26 Thread Felipe Sateler
t; goes away. Is there any update on the switch to nftables? v227 still uses iptables... -- Saludos, Felipe Sateler ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] fstab generator and nfs-client.target

2015-07-27 Thread Felipe Sateler
On 27 July 2015 at 15:58, Lennart Poettering wrote: > On Mon, 27.07.15 15:37, Felipe Sateler (fsate...@debian.org) wrote: > >> On 27 July 2015 at 12:36, Lennart Poettering wrote: >> > On Mon, 27.07.15 15:19, Felipe Sateler (fsate...@debian.org) wrote: >> > >

Re: [systemd-devel] fstab generator and nfs-client.target

2015-07-27 Thread Felipe Sateler
On 27 July 2015 at 12:36, Lennart Poettering wrote: > On Mon, 27.07.15 15:19, Felipe Sateler (fsate...@debian.org) wrote: > >> On Mon, 27 Jul 2015 16:51:02 +0200, Lennart Poettering wrote: >> >> > Coming back to your original question, there are two options: >&g

Re: [systemd-devel] fstab generator and nfs-client.target

2015-07-27 Thread Felipe Sateler
vice is started when the >network is upped. Why isn't WantedBy=remote-fs.target an option? This would make any auto remote mount pull nfs-common, but if none is then it won't be started (unless that part of local-fs doesn't apply to

Re: [systemd-devel] Systemd 215 cannot start journald 219 inside systemd-nspawn

2015-05-15 Thread Felipe Sateler
On 15 May 2015 at 10:15, Lennart Poettering wrote: > On Fri, 15.05.15 10:10, Felipe Sateler (fsate...@debian.org) wrote: > >> > You appear to be using a systemd version without seccomp compiled in, >> > hence you won't get the container behaviour described, and you

Re: [systemd-devel] Systemd 215 cannot start journald 219 inside systemd-nspawn

2015-05-15 Thread Felipe Sateler
On 15 May 2015 at 07:31, Lennart Poettering wrote: > > On Sun, 10.05.15 11:20, Felipe Sateler (fsate...@debian.org) wrote: > > > Hi, > > > > I'm having a problem with a systemd-nspawn'ed container. The guest > > journal will not start and thus I hav

[systemd-devel] Systemd 215 cannot start journald 219 inside systemd-nspawn

2015-05-10 Thread Felipe Sateler
, can this problem be worked around without upgrading the host or downgrading the guest? -- Saludos, Felipe Sateler ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel