On Wednesday 06 February 2013 13:14:00 Kay Sievers wrote:
> This will all be implemented in the future, and work a bit like
> anacron, it just isn't done yet.
>
> Kay
Thanks. It's nice to know that it's intended to be implemented in the future.
Jan
___
On Wed, Feb 6, 2013 at 12:49 PM, Jan Janssen wrote:
> On Tuesday 05 February 2013 11:19:29 David Strauss wrote:
>> On Tue, Feb 5, 2013 at 8:54 AM, Jan Janssen wrote:
>> > It would be nice if timers got scheduled based on their last time they got
>> > triggered.
>>
>> They have always supported th
On Tuesday 05 February 2013 11:19:29 David Strauss wrote:
> On Tue, Feb 5, 2013 at 8:54 AM, Jan Janssen wrote:
> > It would be nice if timers got scheduled based on their last time they got
> > triggered.
>
> They have always supported this, even before we added calendar-based
> support. Check ou
On Tue, Feb 5, 2013 at 8:54 AM, Jan Janssen wrote:
> It would be nice if timers got scheduled based on their last time they got
> triggered.
They have always supported this, even before we added calendar-based
support. Check out the systemd.timer man page.
--
David Strauss
| da...@davidstraus
Hello,
I was wondering how (calendar) timer events triggering occurs on systems that
aren't running 24/7 (e.g. a typical desktop system). To do that I used these
two simple units:
[Unit]
Description=Calendar Test Service
[Service]
Type=oneshot
ExecStart=/
