unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Adriano Peluso <randomlooser@riseup.net>
To: Leo Prikler <leo.prikler@student.tugraz.at>, guix-devel@gnu.org
Subject: Re: blog post about shepher user services
Date: Sat, 22 May 2021 16:42:24 +0200	[thread overview]
Message-ID: <45a41f14d3ac9520c8ba2c008e07016ffdb80ec7.camel@riseup.net> (raw)
In-Reply-To: <271fa5472abb10d85143d023396ce8d8f77c0000.camel@student.tugraz.at>

Il giorno sab, 22/05/2021 alle 15.49 +0200, Leo Prikler ha scritto:
> Hi,
> 
> the blog post you've linked
>   
> https://guix.gnu.org/en/blog/2017/running-system-services-in-containers/
> seems to neither contain mentions of XDG_CONFIG_DIR, nor mcron.
> 
> Did you mean 
>   https://guix.gnu.org/en/blog/2020/gnu-shepherd-user-services/
> instead?

yes, I pasted the wrong one, sorry


> 
> FWIW, $XDG_CONFIG_DIR should be $XDG_CONFIG_HOME, I myself always mix
> those up as well.  

Good to know

> As far as mcron integration is concerned, it doesn't
> look as though this has been done yet and I think work remains to be
> done to have mcron running "as a part of shepherd" rather than as its
> own daemon.  You can right now already run regular cron-jobs through
> mcron just how people did before systemd was a thing.  You just need
> to
> make sure you launch mcron as a user service if you want to go with
> this particular configuration style, otherwise mcron as a system
> service ought to suffice as well.
> 
> Regards,
> Leo
> 

Ok, thanks



  reply	other threads:[~2021-05-22 17:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-22 13:49 blog post about shepher user services Leo Prikler
2021-05-22 14:42 ` Adriano Peluso [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-05-22 10:22 Adriano Peluso

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=45a41f14d3ac9520c8ba2c008e07016ffdb80ec7.camel@riseup.net \
    --to=randomlooser@riseup.net \
    --cc=guix-devel@gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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).