Hello
I am working on time synchronisation issues at boot for systems without
an RTC (using balenaOS on a Raspberry Pi 3) and have some questions
about how journald assigns timestamps to log messages.
When I boot my system and look at the journal I see an initial date/time
for kernel
On Thu, 27 Aug 2020 at 16:11:37 +, u...@net9.ga wrote:
> ExecStart=/bin/bash -c 'set -x; declare -r str="1 2"; echo ${str}; echo $str;
> exit 0;'
This seems to be behaving as documented:
Basic environment variable substitution is supported. Use "${FOO}" as
part of a word, or
27.08.2020 19:11, u...@net9.ga пишет:
> Consider
>
> [Unit]
> Description=Is it looking for ${} construct in the wrong place?
> [Service]
> Type=oneshot
> ExecStart=/bin/bash -c 'set -x; declare -r str="1 2"; echo ${str}; echo $str;
> exit 0;'
>
> When ran, the journal has:
>
> bash[14190]: +
Am 27.08.20 um 18:11 schrieb u...@net9.ga:
> [Unit]
> Description=Is it looking for ${} construct in the wrong place?
> [Service]
> Type=oneshot
> ExecStart=/bin/bash -c 'set -x; declare -r str="1 2"; echo ${str}; echo $str;
> exit 0;'
>
> When ran, the journal has:
>
> bash[14190]: +
Consider
[Unit]
Description=Is it looking for ${} construct in the wrong place?
[Service]
Type=oneshot
ExecStart=/bin/bash -c 'set -x; declare -r str="1 2"; echo ${str}; echo $str;
exit 0;'
When ran, the journal has:
bash[14190]: + declare -r 'str=1 2'
bash[14190]: + echo
bash[14190]: + echo
Am 26.08.20 um 16:01 schrieb Ulrich Windl:
Lennart Poettering schrieb am 26.08.2020 um 15:40
> in
> Nachricht <20200826134031.GA257903@gardel-login>:
>> On Mi, 26.08.20 08:37, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
> wrote:
>>
>>> Hi!
>>>
>>> I see this problem in SLES12
>>> Lennart Poettering schrieb am 26.08.2020 um 15:40
in
Nachricht <20200826134031.GA257903@gardel-login>:
> On Mi, 26.08.20 08:37, Ulrich Windl (ulrich.wi...@rz.uni‑regensburg.de)
wrote:
>
>> Hi!
>>
>> I see this problem in SLES12 (systemd‑228‑157.12.5.x86_64): On boot systemd
> tries to use
