From: "Ludovic Courtès" <ludo@gnu.org>
To: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
Cc: guix-devel@gnu.org
Subject: Re: Announcing shepherd-run
Date: Sat, 09 Nov 2024 23:48:37 +0100 [thread overview]
Message-ID: <87y11syqey.fsf@gnu.org> (raw)
In-Reply-To: <Zyn6fAbfUrghxY7l@3900XT> (Efraim Flashner's message of "Tue, 5 Nov 2024 12:59:08 +0200")
Efraim Flashner <efraim@flashner.co.il> skribis:
> On Mon, Nov 04, 2024 at 11:34:50PM +0100, Ludovic Courtès wrote:
[...]
>> Shepherd 1.0-to-be (current ‘devel’ branch) gained a generic ‘timer’
>> service that does the job the ‘at’ command would do back in the day
>> (before the advent of CD-ROM and the information superhighway):
>>
>> herd schedule timer at 07:00 -- mpg123 alarm.mp3
>>
>> We’re talking about something quite similar, just not delayed, right?
>
> systemd-run has a --timer flag, and I could see adding a flag for
> shepherd-run after shepherd 1.0.
>
> To me the big thing systemd-run brought was being able to launch
> programs from the shell and have it show up in `systemctl --user
> services`, and I'd like to be able to get commands I run from the CLI to
> show up in `herd status` the same way.
Easy. :-) That’s really what ‘herd schedule timer’ does, except it’s
delayed.
> systemd has some more magic I wanted to steal, like being able to launch
> GUI applications from systemd-run.
Trickier I guess, because you need to pass DISPLAY etc.
Food for thought!
Ludo’.
next prev parent reply other threads:[~2024-11-09 22:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-03 13:19 Announcing shepherd-run Efraim Flashner
2024-11-03 15:57 ` Denis 'GNUtoo' Carikli
2024-11-03 18:18 ` Efraim Flashner
2024-11-04 22:34 ` Ludovic Courtès
2024-11-05 10:59 ` Efraim Flashner
2024-11-09 22:48 ` Ludovic Courtès [this message]
2024-11-19 17:17 ` Runciter via Development of GNU Guix and the GNU System distribution.
2024-11-20 21:24 ` Ludovic Courtès
2024-11-21 18:58 ` Efraim Flashner
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=87y11syqey.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=GNUtoo@cyberdimension.org \
--cc=guix-devel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).