I am running Arch-ARM on RPi3. I have noticed when system crashes I cannot
find any related crash log in journal logs.
Arch Linux ARM on RPi3: `Linux 4.4.37-1-ARCH #1 SMP armv7l GNU/Linux`
Systemd: `systemd 232`
`/etc/systemd/journald.conf`:
[Journal]
Storage=persistent
Compress=ye
Hi all,
shameless plug, hope its ok, i've seen people do this,, but that does not
means is ok...
so created a nice python wrapper arround sd-bus.h (and other parts of
libsystemd) the idea is to make accesible to python developer what is
already accesible to c developers.
so you can do stuff like
On Fr, 12.01.18 00:47, 林自均 (johnl...@gmail.com) wrote:
> How about adding an "--order" option to systemctl? With this option,
> systemctl will sort those units by ordering dependencies before submitting
> them. Although I personally wanted this to be the default behavior, I can
> understand compar
Am 12.01.2018 um 17:49 schrieb Lennart Poettering:
On Fr, 12.01.18 10:13, Reindl Harald (h.rei...@thelounge.net) wrote:
Am 12.01.2018 um 08:12 schrieb Andrei Borzenkov:
On Thu, Jan 11, 2018 at 11:41 PM, Reindl Harald wrote:
come on - nobody cares about this bullshit bingo about what are j
On Do, 11.01.18 17:24, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> Ordering dependencies are between jobs. To have any effect here
> systemd must have both start jobs queued concurrently. What is
> unexpected is that multiple services are apparently submitted as
> individual independent jobs,
On Do, 11.01.18 21:41, Reindl Harald (h.rei...@thelounge.net) wrote:
>
> Am 11.01.2018 um 20:27 schrieb Andrei Borzenkov:
> > 11.01.2018 21:56, Reindl Harald пишет:
> > >
> > > it complete unexpected nonsense when i have two services which have a
> > > clear start ordering
> >
> > "services sta
On Do, 11.01.18 17:52, Uoti Urpala (uoti.urp...@pp1.inet.fi) wrote:
> At boot, both would be started as part of the same transaction (same
> would happen here if you started a third.service that depended on both
> first.service and second.service, then second.service would always
> wait). Here sec
eOn Do, 11.01.18 22:30, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> 11.01.2018 22:04, Mantas Mikulėnas пишет:
> >
> > It could, if there was an API call to start multiple jobs at once.
> > (Actually, isn't there one already?...)
> >
>
> None I can find in sources.
There is none. There was
On Fr, 12.01.18 10:13, Reindl Harald (h.rei...@thelounge.net) wrote:
> Am 12.01.2018 um 08:12 schrieb Andrei Borzenkov:
> > On Thu, Jan 11, 2018 at 11:41 PM, Reindl Harald
> > wrote:
> > >
> > > come on - nobody cares about this bullshit bingo about what are jobs,
> > > units
> > > and service
Am 12.01.2018 um 09:55 schrieb Michael Chapman:
On Fri, 12 Jan 2018, Andrei Borzenkov wrote:
And why does it matter? If unit A can be started without unit B, why
does it matter in which order they are started? If unit A can *not* be
started without unit B, it must tell so using Requires or Req
On Thu, Jan 11, 2018 at 11:41 PM, Reindl Harald wrote:
>
> come on - nobody cares about this bullshit bingo about what are jobs, units
> and services
>
I naively believe that understanding software design and how software
works is helpful when discussing said software. May be you are right
and it
On Fri, 12 Jan 2018, Andrei Borzenkov wrote:
12.01.2018 03:47, 林自均 пишет:
How about adding an "--order" option to systemctl? With this option,
systemctl will sort those units by ordering dependencies before submitting
them.
And why does it matter? If unit A can be started without unit B, why
d
On Fri, Jan 12, 2018 at 7:51 AM, 林自均 wrote:
> Hi Andrei,
>
>> If unit A can be started without unit B, why does it matter in which order
>> they are started?
>
> Are you suggesting that After=/Before= must come with Requires= or similar?
What I say is - After/Before is only used when units are ac
On Do, 11.01.18 10:59, 林自均 (johnl...@gmail.com) wrote:
> Hi folks,
>
> I have 2 service unist: first.service and second.service. I configured
> "After=first.service" in second.service. Both services are "Type=oneshot".
>
> If I execute:
>
> # systemctl start first.service second.service
>
> Th
On Fr, 12.01.18 10:16, Francis Moreau (francis.m...@gmail.com) wrote:
> Hello,
>
> I'm wondering why systemctl has the -H option whereas one can achieve
> the same by calling "ssh -- systemctl ...".
Not too much. However it has some benefits, for example it will
auto-page as usual and the pager
Hello,
I'm wondering why systemctl has the -H option whereas one can achieve
the same by calling "ssh -- systemctl ...".
Thanks.
--
Francis
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listin
I had a quick look at the systemd dbus API (which I assume is close to
what systemctl uses) and there are no easy way to queue multiple
"starts" into one job
There is a single StartUnit (+varient) method which can only take a
single unit. no queuing mechanism, way to create ajob without trigge
On Thu, 11 Jan 2018 at 21:41:54 +0100, Reindl Harald wrote:
> come on - nobody cares about this bullshit bingo about what are jobs, units
> and services
Please try to be polite when you are in a situation where you could be
perceived as representing a community. Responses like this to discussion
o
Am 12.01.2018 um 08:12 schrieb Andrei Borzenkov:
On Thu, Jan 11, 2018 at 11:41 PM, Reindl Harald wrote:
come on - nobody cares about this bullshit bingo about what are jobs, units
and services
I naively believe that understanding software design and how software
works is helpful when disc
19 matches
Mail list logo
