ean
> 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 does
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?
FWIW, $XDG_CONFIG_DIR shou
There's this blog post:
https://guix.gnu.org/en/blog/2017/running-system-services-in-containers/
I have 2 observations about it
1) it mentions a XDG_CONFIG_DIR environment variable.
But on my Ubuntu desktop, I find a XDG_CONFIG_DIRS (note the final S)
variable.
This could be confusing to some
Hi Tobias, hi Guix!
Le 05/04, Tobias Geerinckx-Rice a écrit :
> My apologies for not replying sooner. I fail at managing the scarce free
> time I have these days.
I'm not much better, so no need to apologise! ;-)
> Tanguy Le Carrour wrote:
> No, you're right, I'd simply never checked this bef
Tanguy,
My apologies for not replying sooner. I fail at managing the
scarce free time I have these days.
Tanguy Le Carrour wrote:
Cool! :-)
Did you write the "much more snipped" by yourself?
I snipped some definitions for other services, like ibus-daemon
and gpg-agent, because I haven
Hello!
Le 05/01, Tanguy Le Carrour a écrit :
> Le 04/29, Tobias Geerinckx-Rice a écrit :
> > ~ λ cat /home/nckx/.config/shepherd/init.scm (load "services.scm")
> > (register-services emacs gpg-agent ibus-daemon jackd)
> > (action 'shepherd 'daemonize) ; send shepherd into background
> > (for
Hi Tobias
Thanks for your answers!
Le 04/29, Tobias Geerinckx-Rice a écrit :
> > I would love to have some services started when I log in […]
> Note that this is already possible if you want it:
Reading the Shepherd documentation, I was expecting that something like
this was possible, but, corr
Tanguy,
Tanguy Le Carrour wrote:
Hello Guix!
I've just read this thread [1] on the archive and I think it
would be a
great feature! Any update on the topic?!
[1]:
https://lists.gnu.org/archive/html/guix-devel/2019-02/msg00132.html
I would love to have some services started when I log in (
Hello Guix!
I've just read this thread [1] on the archive and I think it would be a
great feature! Any update on the topic?!
[1]: https://lists.gnu.org/archive/html/guix-devel/2019-02/msg00132.html
I would love to have some services started when I log in (tor,
transmission-daemon, mpd, gpg-agent
Joshua Branson writes:
> Can you describe user services a little more for me? It would be nice
> to have the shepherd auto start my emacs... Then I could connect via
> emacsclient. What's the status on that?
Some patches have been sent, but there is quite some work to be do
Pierre Neidhardt writes:
> Fantastic!
>
> This was one of the missing features for user services (e.g. a
> "sync-my-data" service that users would invoke manually).
Can you describe user services a little more for me? It would be nice
to have the shepherd auto start my
Hello Pierre,
> It would also make it possible to fully _initialize_ a user profile (just like
> we initialize the operating-system) with the desired files. For instance, a
> service could synchronize git repositories (e.g. your dotfiles), deploy it,
> synchronize your emails, generate the mlocat
Giovanni Biscuolo writes:
> plz could you confirm what did you deleted to make GNOME run again?
> application_state file or the whole directory?
I deleted the whole directory. I *also* reset my dconf customizations,
but this was not sufficient. I had to delete that directory.
I’ll look for
Hi Ricardo,
plz could you confirm what did you deleted to make GNOME run again?
application_state file or the whole directory?
Ricardo Wurmus writes:
[...]
>> please Ricardo could you attach the relevant debug info?
>
> I don’t have any debug info other than what I posted. I didn’t look at
>
Hi Giovanni,
>> Success! GNOME 3.30 works just fine. The gnome-shell segfaulted(!)
>> because of stale state
>
> this is one of the worst bugs a user can experience, and very few users
> are able to debug it properly (and experienced users like me find it
> very time wasting to debug them)
Ye
Hi all,
Ricardo Wurmus writes:
[...]
> Success! GNOME 3.30 works just fine. The gnome-shell segfaulted(!)
> because of stale state
this is one of the worst bugs a user can experience, and very few users
are able to debug it properly (and experienced users like me find it
very time wasting to
a user-specific Shepherd, not the root
user's Shepherd? Perhaps a user profile should also have a "user
services activation script", like how an operating system declaration
has operating-system-activation-script (in gnu/system.scm)?
I personally wouldn't mind if this stuff (
configuration
> file.
Indeed, that’s a neat hack! And it ties software and service
deployment, which is great.
> ;; the next two are copied from (gnu services shepherd) because:
>
> ;; * (gnu services shepherd)'s version of shepherd-configuration-file
> ;; is for the pid1 shep
Attached is a manifest file which allows a user to write a
shepherd-service like the following:
(define redshift-service
(shepherd-service
(provision '(redshift))
(modules `((gnu packages xdisorg)
,@%default-modules))
(start #~(make-forkexec-constructor
(list
Hello Danny,
Danny Milosavljevic skribis:
> On Tue, 13 Jun 2017 10:06:16 +0200
> l...@gnu.org (Ludovic Courtès) wrote:
>
>> The ‘delete-file’ was to avoid EADDRINUSE but I wonder if it’s really a
>> good idea.
>
> Not a good idea.
>
> We should just put the shepherd socket somewhere in /run/user
that
> > shepherd will inherit. Probably not that bad if invoked early enough.
>
> Currently that’s what I do: my ~/.xinitrc runs shepherd and that’s it.
Yeah, me too. That's how I found the bug... when I logged in to multiple seats
suddenly I had a LOT of duplicate "user" services running :)
Hello!
Danny Milosavljevic skribis:
> For a real user shepherd, it would be nice if when I logged in twice using
> the same user account (without logging out in-between - so resulting in two
> sessions of that user) it would still only have one shepherd instance for
> that user account in tot
Hello!
Mathieu Othacehe skribis:
> I wrote a first draft of user services a month ago. The idea here is
> that guix user -r user-manifest.scm generates a script that lauches a
> user shepherd.
>
> For instance with the following user-manifest.scm :
>
> (define (re
Hi Danny,
> Or should we just expect the user to put a (shepherd with fix)
> invocation into their HOME startup scripts like .xinitrc ?
I wrote a first draft of user services a month ago. The idea here is
that guix user -r user-manifest.scm generates a script that lauches a
user shepherd
Hi,
I'm revisiting this topic because I want to have a dbus user bus to be
available as "${XDG_RUNTIME_DIR}/bus".
> > With the attached patch, it is possibe to use (gnu services herd) to
> > interact with a user shepherd instance.
Nice! It works!
But while testing it I noticed:
For a real us
>> Happy hacking! :-)
>> Ludo’.
>
> Yay! Welcome Mathieu!
Thanks Ricardo and Ludo !
Pushed as 5e03b122cf295d24e01861ca942505d47f9aa59e.
Ludovic Courtès writes:
> Hi!
>
> Mathieu Othacehe skribis:
>
>>> Could you create an account on Savannah, add the OpenPGP public key
>>> you’ll use to sign commits there, and let us know when you’re done with
>>> a signed message? Looks like we should be able to increase the
>>> bandwidth. :
Mathieu Othacehe skribis:
> From caf7d9f5a7875663623b24662c1c23b99e60c5ad Mon Sep 17 00:00:00 2001
> From: Mathieu Othacehe
> Date: Fri, 28 Apr 2017 17:09:53 +0200
> Subject: [PATCH] services: herd: Make %shepherd-socket-file a parameter and
> export it.
>
> * gnu/services/herd.scm (%shepherd-s
Hi!
Mathieu Othacehe skribis:
>> Could you create an account on Savannah, add the OpenPGP public key
>> you’ll use to sign commits there, and let us know when you’re done with
>> a signed message? Looks like we should be able to increase the
>> bandwidth. :-)
>
> Thanks :) I created the accoun
Hi Ludo,
> Neat, sounds like a good plan!
Great !
> Could you create an account on Savannah, add the OpenPGP public key
> you’ll use to sign commits there, and let us know when you’re done with
> a signed message? Looks like we should be able to increase the
> bandwidth. :-)
Thanks :) I crea
Hello Mathieu,
Mathieu Othacehe skribis:
>> Agreed. A ‘guix user’ tool (or similar) could talk to the user’s
>> Shepherd instance to upgrade user services like
>> ‘upgrade-shepherd-services’ does in (guix scripts system).
>
> With the attached patch, it is possibe to us
Hi,
> Agreed. A ‘guix user’ tool (or similar) could talk to the user’s
> Shepherd instance to upgrade user services like
> ‘upgrade-shepherd-services’ does in (guix scripts system).
With the attached patch, it is possibe to use (gnu services herd) to
interact with a user shepherd
t; ))
>>
>> or similar :)
>
> While I’m not a fan of Guix-specific aliases, I think it’s not a bad
> idea to use Guix for user configurations. I’m tired of having to keep
> track of a set of custom configuration files scattered all over the
> place, but I’m not su
Mekeor Melire writes:
> Mathieu Othacehe writes:
>
>>>> But you can start your own shepherd under your user account and have that
>>>> shepherd manage user services - it's nice.
>>
>> Thank you Danny for the details procedure. I'll use t
Mathieu Othacehe writes:
>>> But you can start your own shepherd under your user account and have that
>>> shepherd manage user services - it's nice.
>
> Thank you Danny for the details procedure. I'll use that for now !
>
>> Surely we could do bette
Hi guys,
>> But you can start your own shepherd under your user account and have that
>> shepherd manage user services - it's nice.
Thank you Danny for the details procedure. I'll use that for now !
> Surely we could do better, like providing unprivileged users wi
expects when the child dies.
I've also found that shepherd doesn't properly watch a process that uses
#:pid-file. I start my emacs with --daemon using shepherd and have it
create a pid file, but if emacs dies shepherd doesn't restart it for me.
Other than this, everything else about
#x27;s not being brought back up.
>
> But you can start your own shepherd under your user account and have that
> shepherd manage user services - it's nice.
That’s exactly what I do.
Surely we could do better, like providing unprivileged users with a tool
akin to ‘guix system recon
u can start your own shepherd under your user account and have that
shepherd manage user services - it's nice.
Create a file ${XDG_CONFIG_HOME-.config}/shepherd/init.scm and put your
services there:
(use-modules (shepherd service))
(define redshift (make #:provides '(redshift) #:start ...
Hi Guix,
I just a wrote a small service for redshift¹. Redshift is a program
adjusting color temperature of the screen according to surroundings.
This program needs to communicate to X, so DISPLAY and XAUTHORITY must
be set correctly.
The only way I found to make my service work is something ve
40 matches
Mail list logo
