The simplest way is to add Wants=bar.service and After=bar.service to
foo.service.
Отправлено с iPhone
> 20 марта 2018 г., в 7:44, Evan Klitzke написал(а):
>
> I am wondering how to create a cascade of oneshot units that should run
> on a timer. What I'm imagining is something like the followi
Отправлено с iPhone
> 20 марта 2018 г., в 8:15, Andrei Borzenkov написал(а):
>
> The simplest way is to add Wants=bar.service and After=bar.service to
> foo.service.
I mean of course Before=bar.service
>
> Отправлено с iPhone
>
>> 20 марта 2018 г., в 7:44, Evan Klitzke написал(а):
>>
>
Andrei Borzenkov writes:
The simplest way is to add Wants=bar.service and After=bar.service to
foo.service.
I mean of course Before=bar.service
Indeed that seems to work! Thanks for your help.
___
systemd-devel mailing list
systemd-devel@lists.fre
naive question, but why are you not using systemd's handling of hardware
daemon (see man:system.conf for how to activate it)
basically, systemd is monitored by the hardware daemon and systemd
monitors (via its software watchdog) any service that wants to be monitored
this creates a better cha
On Mo, 19.03.18 14:39, Alexander 'Leo' Bergolth (l...@strike.wu.ac.at) wrote:
> Hi!
>
> I am using the software watchdog daemon together with a watchdog device in
> "nowayout" mode.
> Thus once started, the watchdog daemon should never be stopped or the box
> will be rebooted.
>
> watchdog.ser
On Do, 15.03.18 07:02, Matthijs van Duin (matthijsvand...@gmail.com) wrote:
> While studying a bit how journal works, I noticed something odd:
>
> My understanding of the boot_id field in the file header is that it should
> reflect the boot_id of the tail entry, to allow correct interpretation of
gOn Do, 08.03.18 14:39, ChenQi (qi.c...@windriver.com) wrote:
> Hi All,
>
> I'd like to know if systemd community thinks that adding support for
> relative values in configuration is a good idea.
Depends on which precise options you are talking of? But yeah, in general
would be very welcome for
On Fr, 09.03.18 10:30, Dimitri John Ledkov (x...@ubuntu.com) wrote:
> I have a request to start/stop/restart the dhcp lease client, and/or
> run networkd dhcp client stand alone, or somehow serialize dhcpclient
> lease and inject that for networkd-dhcp to pick that up and restart.
>
> For example
On Mi, 14.03.18 23:05, Martin Townsend (mtownsend1...@gmail.com) wrote:
> Hi,
>
> I'm getting the following log when booting with IMA/EVM and SMACK
> enabled. Before I start delving into IMA and SMACK does anyone know
> of any fixes that have gone into systemd that would fix the problem
> I'm se
On Fr, 16.03.18 09:27, prashantkumar dhotre (prashantkumardho...@gmail.com)
wrote:
> Thanks but I want to sigkill my services only during system shutdown and
> not on normal service stop 'systemctl myservice stop'.
> so I can not use ' KillSignal' setting. Is there any other way ?
Nope there is
On Fr, 16.03.18 09:13, prashantkumar dhotre (prashantkumardho...@gmail.com)
wrote:
> Hi
> I see that default reboot/systemctl reboot command issues SIGTERM to my
> apps and hence it is doing graceful stop of apps and this may take some
> time and hence shutdown time may be little longer.
>
> I a
Hi,
If systemd is running as the init process on a system that uses selinux,
then mysterious bad things are likely to happen if the selinux context
is not init_t. For instance:
https://bugzilla.redhat.com/show_bug.cgi?id=1520580#c13
So, I'd like to see systemd diagnose this situation. Pleas
On Tue, Mar 20, 2018 at 12:52 AM, John Ioannidis wrote:
> I want to have a service with several instances, each of which has a
> configuration file; when configuration files appear and disappear, I want
> the corresponding instances to be created and started, and die,
> respectively, and in partic
On 03/20/2018 12:57 AM, Peter A. Bigot wrote:
On 03/19/2018 04:17 PM, Lennart Poettering wrote:
Would be great if you could rework it accordingly and submit it as PR.
https://github.com/systemd/systemd/pull/8494
I've addressed most of the review comments but before pushing a new
version wa
On Tue, Mar 20, 2018 at 8:47 AM, Andrei Borzenkov
wrote:
> On Tue, Mar 20, 2018 at 12:52 AM, John Ioannidis
> wrote:
>
>
> > I can get them to start the first time, but they do not stop when
> > configuration files change. If I systemctl daemon-reload, the links in
> > /run/systemd/system-genera
On Di, 20.03.18 04:26, John Reiser (jrei...@bitwagon.com) wrote:
> Hi,
>
> If systemd is running as the init process on a system that uses selinux,
> then mysterious bad things are likely to happen if the selinux context
> is not init_t. For instance:
>https://bugzilla.redhat.com/show_bug.cg
On Di, 20.03.18 08:54, Peter A. Bigot (p...@pabigot.com) wrote:
> On 03/20/2018 12:57 AM, Peter A. Bigot wrote:
> > On 03/19/2018 04:17 PM, Lennart Poettering wrote:
> > > Would be great if you could rework it accordingly and submit it as PR.
> >
> > https://github.com/systemd/systemd/pull/8494
>
On Di, 20.03.18 11:05, John Ioannidis (systemd-de...@tla.org) wrote:
> On Tue, Mar 20, 2018 at 8:47 AM, Andrei Borzenkov
> wrote:
>
> > On Tue, Mar 20, 2018 at 12:52 AM, John Ioannidis
> > wrote:
> >
> >
> > > I can get them to start the first time, but they do not stop when
> > > configuration
On Mi, 14.03.18 00:22, Reindl Harald (h.rei...@thelounge.net) wrote:
>
>
> Am 14.03.2018 um 00:00 schrieb Ryan Gonzalez:
> > You literally sent this out 1 minute after posting the bug. At least
> > give it time to breath first...
>
> what the hell - sorry for having bad news which i saw from th
Am 20.03.2018 um 17:26 schrieb Lennart Poettering:
On Mi, 14.03.18 00:22, Reindl Harald (h.rei...@thelounge.net) wrote:
Am 14.03.2018 um 00:00 schrieb Ryan Gonzalez:
You literally sent this out 1 minute after posting the bug. At least
give it time to breath first...
what the hell - sorry f
On Di, 20.03.18 18:06, Reindl Harald (h.rei...@thelounge.net) wrote:
>
>
> Am 20.03.2018 um 17:26 schrieb Lennart Poettering:
> > On Mi, 14.03.18 00:22, Reindl Harald (h.rei...@thelounge.net) wrote:
> > >
> > > Am 14.03.2018 um 00:00 schrieb Ryan Gonzalez:
> > > > You literally sent this out 1
Am 20.03.2018 um 18:13 schrieb Lennart Poettering:
On Di, 20.03.18 18:06, Reindl Harald (h.rei...@thelounge.net) wrote:
Am 20.03.2018 um 17:26 schrieb Lennart Poettering:
On Mi, 14.03.18 00:22, Reindl Harald (h.rei...@thelounge.net) wrote:
Am 14.03.2018 um 00:00 schrieb Ryan Gonzalez:
You
On Di, 20.03.18 18:21, Reindl Harald (h.rei...@thelounge.net) wrote:
> > > you understand that repsonses like "My problem is sooo important, I need
> > > to
> > > pester the whole systemd-devel mailing list with a regular bug report"
> > > making people trying to help get aware about problems ups
I'm working on: https://github.com/ostreedev/ostree/issues/545
TL;DR:
libostree is an image-like update system, and I want to take some
actions at system shutdown time, specifically performing a "snapshot+merge"
of /etc after most other services are shut down. The way ostree
handles /etc (IMO a lo
On Tue, 20 Mar 2018 at 19:16:59 +, Mantas Mikulėnas wrote:
> On Tue, Mar 20, 2018, 21:09 Colin Walters wrote:
> Another way I've thought about handling this is to basically invert things
> so that
> we have a "stub" unit that starts on bootup, and its ExecStop does the
> real
>
On Di, 20.03.18 15:09, Colin Walters (walt...@verbum.org) wrote:
> Another way I've thought about handling this is to basically invert things so
> that
> we have a "stub" unit that starts on bootup, and its ExecStop does
> the real work:
This is the correct and recommended way to do this.
> [Un
On Tue, Mar 20, 2018, 21:09 Colin Walters wrote:
> I'm working on: https://github.com/ostreedev/ostree/issues/545
> TL;DR:
> libostree is an image-like update system, and I want to take some
> actions at system shutdown time, specifically performing a "snapshot+merge"
> of /etc after most other s
On Tue, Mar 20, 2018, at 3:25 PM, Lennart Poettering wrote:
> On Di, 20.03.18 15:09, Colin Walters (walt...@verbum.org) wrote:
>
> > Another way I've thought about handling this is to basically invert things
> > so that
> > we have a "stub" unit that starts on bootup, and its ExecStop does
> >
Hi,
*Summary:*I'm trying to debug not being able to get an IPv6 DHCPv6 address
when using systemd-networkd (v229 Ubuntu 16.04) with an LTE Modem. It'd be
really great if someone could at least validate my config file below!
matt@crash-override ~ $ cat /etc/systemd/network/10-usb.network
[Match]
On Di, 20.03.18 15:36, Colin Walters (walt...@verbum.org) wrote:
>
>
> On Tue, Mar 20, 2018, at 3:25 PM, Lennart Poettering wrote:
> > On Di, 20.03.18 15:09, Colin Walters (walt...@verbum.org) wrote:
> >
> > > Another way I've thought about handling this is to basically invert
> > > things so
Hello!!
Recently, I was trying to help out someone on IRC move some sysvinit
scripts over to systemd units, and there was one interesting issue that
came up. Many older daemons will create sockets at some unspecified point
in their startup sequence, with no indication of when this occurs. In t
On Di, 20.03.18 16:08, Ryan Gonzalez (rym...@gmail.com) wrote:
> Hello!!
>
> Recently, I was trying to help out someone on IRC move some sysvinit scripts
> over to systemd units, and there was one interesting issue that came up.
> Many older daemons will create sockets at some unspecified point i
32 matches
Mail list logo
