From: Pierre Neidhardt <ambrevar@gmail.com>
To: Benjamin Slade <slade@jnanam.net>
Cc: help-guix@gnu.org
Subject: Re: mcron
Date: Sun, 05 Aug 2018 10:45:26 +0200 [thread overview]
Message-ID: <87h8k9b3rt.fsf@gmail.com> (raw)
In-Reply-To: <87pnyxiqz4.fsf@jnanam.net>
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
Yes, Vixie syntax is supported there too!
See "(mcron) Vixie Syntax".
But if you can grasp the Lisp syntax instead, I'd recommend you for it, it's
much more flexible. After all, it's the sole raison-d'être of mcron with regard
to cron :)
I think your solution to "every N minute" is correct.
Cheers!
--
Pierre Neidhardt
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2018-08-05 8:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 5:33 mcron Benjamin Slade
2018-08-04 8:44 ` mcron Pierre Neidhardt
2018-08-04 21:16 ` mcron Benjamin Slade
2018-08-04 22:02 ` mcron Pierre Neidhardt
2018-08-05 0:42 ` mcron Benjamin Slade
2018-08-05 8:45 ` Pierre Neidhardt [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h8k9b3rt.fsf@gmail.com \
--to=ambrevar@gmail.com \
--cc=help-guix@gnu.org \
--cc=slade@jnanam.net \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).