This feels like something I should be easily able to answer from
documentation/Google, and failing that from somewhere like
StackOverflow, without troubling systemd-devel, but all my efforts
have thus far failed [1]
What is the correct way to ensure a script runs to completion before
any
Thanks again for your in depth reply.
> it's a very different kind of language, as these specifiers are
> defined by systemd itself
Maybe someday someone will find a safe way to inject addtionally,
arbitrary values into systemd. There are still some free letters left
that can be prefixed
On Sat, Jun 27, 2020 at 11:42:00AM +0100, Mark Rogers wrote:
> On Sat, 27 Jun 2020 at 11:06, Zbigniew Jędrzejewski-Szmek
> wrote:
> > You should use Before=network-pre.target, Wants=network-pre.target.
>
> Thanks, tried that but still not working:
>
> $ journalctl -b | grep -Ei
On Sat, 27 Jun 2020 at 11:51, Dave Howorth wrote:
> A Pi doesn't normally have an RTC, so the mixup usually takes place
> when the time is updated via NTP I believe. Do you have an RTC?
Yes I do have an RTC. At that point in the logs dhcpcd hasn't started
so it must be from the RTC (although
Just a wild guess, but I'd start with a combination of one of those:
# -
[Unit]
Description=my service
Before=network.target
Before=systemd-networkd.service
Before=network-online.target
Before=systemd-networkd-wait-online.service
...
[Install]
WantedBy=Basic.target
# -
Probably
On Sat, 27 Jun 2020 at 13:04, Andrei Borzenkov wrote:
> All other units that implement networking must have
> After=network-pre.target for the above to do anything. Do they?
.. and ..
On Sat, 27 Jun 2020 at 13:08, Michael Chapman wrote:
> It could very well be because of the dhcpcd.service
On Sat, 27 Jun 2020 11:42:00 +0100
Mark Rogers wrote:
> On Sat, 27 Jun 2020 at 11:06, Zbigniew Jędrzejewski-Szmek
> wrote:
> > You should use Before=network-pre.target,
> > Wants=network-pre.target.
>
> Thanks, tried that but still not working:
>
> $ journalctl -b | grep -Ei
On Sat, Jun 27, 2020 at 09:34:00AM +0100, Mark Rogers wrote:
> I have tried multiple approaches so far but by current service file
> looks like this:
>
> [Unit]
> Description=Config generation from DB
> Before=networking.service
You should use Before=network-pre.target, Wants=network-pre.target.
On Sat, 27 Jun 2020 at 11:06, Zbigniew Jędrzejewski-Szmek
wrote:
> You should use Before=network-pre.target, Wants=network-pre.target.
Thanks, tried that but still not working:
$ journalctl -b | grep -Ei '(db2config|dhcpcd)'
Feb 14 10:12:03 localhost systemd[1]: Starting dhcpcd on all
27.06.2020 13:42, Mark Rogers пишет:
> On Sat, 27 Jun 2020 at 11:06, Zbigniew Jędrzejewski-Szmek
> wrote:
>> You should use Before=network-pre.target, Wants=network-pre.target.
>
> Thanks, tried that but still not working:
>
All other units that implement networking must have
On Sat, 27 Jun 2020, Mark Rogers wrote:
> On Sat, 27 Jun 2020 at 11:06, Zbigniew Jędrzejewski-Szmek
> wrote:
> > You should use Before=network-pre.target, Wants=network-pre.target.
>
> Thanks, tried that but still not working:
It could very well be because of the dhcpcd.service you're using.
I
Am 27.06.20 um 16:54 schrieb Mark Rogers:
> Ah, therein lies my failing - I assumed OS supplied units wouldn't
> need adapting...
>
> Adding After=network-pre.target to dhcpcd.service seems to have
> resolved it, and taught me a lesson in the process.
as often it depends - on machines with
is this a dracut or systemd bug in Fedora 32?
the other failing services at bottom are a direct reuslt of this while
everything seems to work fine, but i can't stand "failed" stuff when
consider a dist-upgrade
--
[root@rawhide ~]# systemctl status
Hello,
I noticed that mounting partition takes more time on yocto thud regarding
rocko.
I checked the dev-mmcblk0p2.device in my case using systemd-bootchart.
Is there any reason why this mouting delay was increased?
Where the dev-mmcblk0p2.device comes from? I am not able to locate it in
14 matches
Mail list logo
