all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Attila Lendvai <attila@lendvai.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Sergey Trofimov <sarg@sarg.org.ru>,
	62401@debbugs.gnu.org, paren@disroot.org, andrew@trop.in,
	guix-devel@gnu.org
Subject: Re: Automatically mapping services from System to Home
Date: Tue, 28 Mar 2023 19:59:03 +0000	[thread overview]
Message-ID: <c5fO0YPa379sD5mE3Zbq8jhYF6LHKZivfkH8WOHp_nIPyvH0N5CBkEn5o21xJAGeJknbTKcepR1DscRaP0CgZTC-uMCgBnxw8fg7fYLlIeE=@lendvai.name> (raw)
In-Reply-To: <87edp8g88j.fsf@gnu.org>

> Thoughts?

my gut reaction is that whatever the automatic mapping does should be captured/reified into the code that defines a service... factoring out the common parts, and adding on top of that whatever is necessary in the two different contexts.

but then i'm not sure i fully understand the differences between these two contexts, and i don't have a proposal.diff either, so...

BTW, what are the differences?

 - a possible call to setuid/setgid, and their values in the config if
   the service is not to be started as root?

 - the default values of the config file and log file(s)? possibly
   some service-specific values in the config whose default value
   depend on the user/group under which the service is running?

maybe the user/group should be a mandatory value under the hood, and the service code should dispatch on their values and the current effective user/group id, and act accordingly?

what am i missing?

-- 
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
“The moral law is one of the basic laws of the universe. It is likewise called the principle of Karma, the result of cause and effect, or action and reaction. There is nothing vindictive about this principle. It works impersonally like any law of nature. As the fruit is contained in the seed, so the consequences are inherent in the act. This principle guides the destinies of both people and nations. Knowledge of this principle gives human beings the power to control our own destiny.”
	— Thor Kiimaletho



  reply	other threads:[~2023-03-28 19:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  8:10 [bug#62401] [PATCH] home: Add home-syncthing-service-type Sergey Trofimov
2023-03-28 15:58 ` Ludovic Courtès
2023-03-28 19:29   ` Sergey Trofimov
2023-03-29 16:35     ` Bruno Victal
2023-03-28 16:18 ` Automatically mapping services from System to Home Ludovic Courtès
2023-03-28 19:59   ` Attila Lendvai [this message]
2023-03-29 15:21   ` Bruno Victal
2023-08-07  9:50     ` [bug#62401] [PATCH] home: Add home-syncthing-service-type Ludovic Courtès

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='c5fO0YPa379sD5mE3Zbq8jhYF6LHKZivfkH8WOHp_nIPyvH0N5CBkEn5o21xJAGeJknbTKcepR1DscRaP0CgZTC-uMCgBnxw8fg7fYLlIeE=@lendvai.name' \
    --to=attila@lendvai.name \
    --cc=62401@debbugs.gnu.org \
    --cc=andrew@trop.in \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=paren@disroot.org \
    --cc=sarg@sarg.org.ru \
    /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.