all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: Felix Lechner via <help-guix@gnu.org>
Cc: Felix Lechner <felix.lechner@lease-up.com>
Subject: Re: How to add the timer-trigger-action to a shepherd service?
Date: Wed, 18 Dec 2024 15:05:10 +0100	[thread overview]
Message-ID: <877c7xaxyh.fsf@wolfsden.cz> (raw)
In-Reply-To: <87y10fi4ix.fsf@lease-up.com> (Felix Lechner via's message of "Mon, 16 Dec 2024 15:36:54 -0800")

[-- Attachment #1: Type: text/plain, Size: 892 bytes --]

Hello,

Felix Lechner via <help-guix@gnu.org> writes:

> Hi Tomas,
>
> On Mon, Dec 16 2024, Tomas Volf wrote:
>
>> what to put into the (actions) field
>
> Please try this:
>
>    (actions
>     (list (shepherd-action
>            (name 'trigger)
>            (documentation "Trigger the action associated with this timer.")
>            (procedure #~(identity trigger-timer)))))

I see, so basically from shepherd use just the procedure, and craft the
rest of the action by hand.  Thank you for the advice. :)

>
> You can see my full timer definitions here. [1]
>
> Kind regards
> Felix
>
> [1] https://codeberg.org/lechner/system-config/src/commit/4335818ba8da818f21810b5b402db51c77d3b344/host/wallace-server/operating-system.scm#L660-L664
>

-- 
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]

  reply	other threads:[~2024-12-18 14:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-16 22:53 How to add the timer-trigger-action to a shepherd service? Tomas Volf
2024-12-16 23:36 ` Felix Lechner via
2024-12-18 14:05   ` Tomas Volf [this message]
2024-12-16 23:43 ` Jake
2024-12-18 14:06   ` Tomas Volf

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877c7xaxyh.fsf@wolfsden.cz \
    --to=~@wolfsden.cz \
    --cc=felix.lechner@lease-up.com \
    --cc=help-guix@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.