On Thu, Oct 28, 2021 at 10:25 PM Andrei Borzenkov
wrote:
> On 29.10.2021 04:54, Han wrote:
> > Hi,
> >
> > I'm a newbie to systemd. I encountered a strange problem when using
> > systemd user
> > service in Debian 10 (hardware: Raspberry Pi 4), systemd version 241.
> >
> > I posted this question
On 29.10.2021 04:54, Han wrote:
> Hi,
>
> I'm a newbie to systemd. I encountered a strange problem when using
> systemd user
> service in Debian 10 (hardware: Raspberry Pi 4), systemd version 241.
>
> I posted this question on stackoverflow but didn't get answers yet. Hence
> trying to ask here.
On Thu, Oct 28, 2021 at 4:27 PM Mitchel Humpherys
wrote:
>
> On Thu, Oct 28, 2021 at 3:18 PM Michael Biebl wrote:
> >
> > Might be another instance of
> > https://github.com/systemd/systemd/issues/2913
> >
> > You can verify by checking your whole journal, not just "-u
> > tee_test.service".
>
Hi,
I'm a newbie to systemd. I encountered a strange problem when using
systemd user
service in Debian 10 (hardware: Raspberry Pi 4), systemd version 241.
I posted this question on stackoverflow but didn't get answers yet. Hence
trying to ask here. My apologies if this is too basic.
1. I
On Thu, Oct 28, 2021 at 3:18 PM Michael Biebl wrote:
>
> Might be another instance of
> https://github.com/systemd/systemd/issues/2913
>
> You can verify by checking your whole journal, not just "-u tee_test.service".
That's it!!! Damn, the userspace workarounds are a little nasty...
On the
Might be another instance of
https://github.com/systemd/systemd/issues/2913
You can verify by checking your whole journal, not just "-u tee_test.service".
Am Do., 28. Okt. 2021 um 21:54 Uhr schrieb Mitchel Humpherys
:
>
> On Thu, Oct 28, 2021 at 12:35 AM Ulrich Windl
> wrote:
> >
> > ANother
On Thu, Oct 28, 2021 at 12:35 AM Ulrich Windl
wrote:
>
> ANother random idea: Did you experiment with tee option "--output-error=..."?
Just gave that a shot and didn't get any additional output :(
There is A.timer and its A.service, and B.timer and B.service.
Both A and B do not know about each other per default.
Both timers fire in their own cadence.
Both services have their unpredictable time until they finish.
So it may happen that A.service is started while B.service is still active.
On Do, 28.10.21 11:46, Arian van Putten (arian.vanput...@gmail.com) wrote:
> Indeed it mentions it; but after careful reading there is no normative
> suggestion to actually adhere to it. (no SHOULD and definitely not a MUST,
> not even a RECOMMENDED).
>
> They just say that to increase
Indeed it mentions it; but after careful reading there is no normative
suggestion to actually adhere to it. (no SHOULD and definitely not a MUST,
not even a RECOMMENDED).
They just say that to increase interoperability no more than 53 bits of
integer precision should be assumed without making a
ANother random idea: Did you experiment with tee option "--output-error=..."?
>>> Mitchel Humpherys schrieb am 27.10.2021 um 18:50
in
Nachricht
:
> On Wed, Oct 27, 2021 at 1:52 AM Colin Guthrie wrote:
>>
>> Mitchel Humpherys wrote on 26/10/2021 21:16:
>> > On my Manjaro and Ubuntu systems I'm
>>> Arian van Putten schrieb am 26.10.2021 um 10:41
>>> in
Nachricht
:
> Hey list,
>
> I'm reading the https://systemd.io/USER_RECORD/ spec and I have a question
>
> There are some fields in the USER_RECORD spec which are described as
> "unsigned 64 bit integer values". Specifically the
12 matches
Mail list logo
