Hi,
was it even considered initially to have proper timezones support in timers?
Or perhaps it is somewhere in the roadmap?
In particular, I'm speaking of `[Timer] OnCalendar`
--
With best regards, Ivan Kurnosov
___
systemd-devel mailing
19:11, Lennart Poettering
wrote:
> On Di, 05.09.17 09:41, Ivan Kurnosov (zer...@zerkms.ru) wrote:
>
> > Hi,
> >
> > was it even considered initially to have proper timezones support in
> timers?
> >
> > Or perhaps it is somewhere in the roadmap?
> >
>
17 at 01:25, Lennart Poettering
wrote:
> On Mi, 06.09.17 13:18, Mantas Mikulėnas (graw...@gmail.com) wrote:
>
> > On Wed, Sep 6, 2017 at 12:58 PM, Ivan Kurnosov wrote:
> >
> > > I've started working on it (as a crazy experiment for myself primarily)
> >
ummer time change.
Implementation might be improved further via a small refactoring to remove
the `CalendarSpec::utc` field, since it effectively is not necessary now,
given that one may use `spec->timezone = "UTC";` instead.
I'm looking for your feedback,
thanks.
On 7 September
name.
May 18 08:30:46 hostname systemd[1]: Started servicename.
May 18 08:30:46 hostname servicename[7739]: foo
What would be a way to **guarantee** journald received the `stdout`, if any?
--
With best regards, Ivan Kurnosov
___
systemd-devel m
That's it.
Yep, I can see it in the `journalctl` but it's not in `journalctl -u
servicename`
Thanks
On 18 May 2018 at 11:44, Michael Biebl wrote:
> 2018-05-17 23:02 GMT+02:00 Ivan Kurnosov :
>
> > Here is the example of the `journald` output for the service:
>
>
I'm observing it on the ubuntu bionic that comes with systemd 237
On 19 May 2018 at 07:27, Lennart Poettering wrote:
> On Fr, 18.05.18 09:02, Ivan Kurnosov (zer...@zerkms.ru) wrote:
>
> > Hi,
> >
> > I originally asked this question on the stackoverflow (
&g
