From 89c8e31ec07b5874e76c96ca9a1ec8af55491538 Mon Sep 17 00:00:00 2001 From: grindhold Date: Sat, 21 Sep 2019 13:29:43 +0200 Subject: [PATCH] =?UTF-8?q?fix=20typo=20in=20cmdline-arg=20'priviledge'?= =?UTF-8?q?=E2=86=92'privilege'?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- doc/gnunet-setup.1 | 6 +++--- src/setup/gnunet-setup.c | 4 ++-- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/gnunet-setup.1 b/doc/gnunet-setup.1 index 8213c558..5e901ce2 100644 --- a/doc/gnunet-setup.1 +++ b/doc/gnunet-setup.1 @@ -8,7 +8,7 @@ gnunet\-setup \- a gtk interface for configuring GNUnet .PP gnunet\-setup is a gtk+ based GUI for configuring GNUnet. -The first time you run gnunet\-setup, the goal will typically be to configure the peer, that is, the set of processes that always run in the background. Those processes should run as user "gnunet" and thus gnunet\-setup should be run as user "gnunet" for this step. Use the "\-e" option to enable automatic priviledge escalation using gksu (if supported by your system). Alternatively, you can of course run gnunet\-setup from the "gnunet" system user account or even as "root". If you see a tab "General", you did start gnunet\-setup correctly to configure the peer. You should now be able to configure which subsystems of GNUnet you want to enable, which databases to use and what your network configuration looks like. After these steps are complete, you should be able to start your peer using "gnunet\-arm". +The first time you run gnunet\-setup, the goal will typically be to configure the peer, that is, the set of processes that always run in the background. Those processes should run as user "gnunet" and thus gnunet\-setup should be run as user "gnunet" for this step. Use the "\-e" option to enable automatic privilege escalation using gksu (if supported by your system). Alternatively, you can of course run gnunet\-setup from the "gnunet" system user account or even as "root". If you see a tab "General", you did start gnunet\-setup correctly to configure the peer. You should now be able to configure which subsystems of GNUnet you want to enable, which databases to use and what your network configuration looks like. After these steps are complete, you should be able to start your peer using "gnunet\-arm". It is recommended that "/etc/gnunet.conf" should be a world\-readable copy of the peer's GNUnet configuration. Note that GNUnet configuration files (as generated by gnunet\-setup) only contain those values that differ from the defaults. Also note that "gnunet\-arm" will by default look for a configuration in "$HOME/.config/gnunet.conf" (or, "$XDG_CONFIG_DIR/gnunet.conf" if "$XDG_CONFIG_DIR" is set); thus, if your configuration is in "/etc/gnunet.conf", you have to pass "\-c /etc/gnunet.conf" to gnunet\-arm or set "$XDG_CONFIG_DIR" to "/etc/". @@ -16,8 +16,8 @@ It is recommended that "/etc/gnunet.conf" should be a world\-readable copy of th \fB\-c \fIFILENAME\fR, \fB\-\-config=FILENAME\fR load config file (default: ~/.config/gnunet.conf) .TP -\fB\-e, \fB\-\-elevate\-priviledges\fR -Try to elevate priviledges to run gnunet\-setup as user "gnunet". This option is only available if libgksu\-support was found on your system. It is ignored if gnunet\-setup is run as user "root" or "gnunet" already. If "gksu" fails, gnunet\]-setup is run as the current user. +\fB\-e, \fB\-\-elevate\-privileges\fR +Try to elevate privileges to run gnunet\-setup as user "gnunet". This option is only available if libgksu\-support was found on your system. It is ignored if gnunet\-setup is run as user "root" or "gnunet" already. If "gksu" fails, gnunet\]-setup is run as the current user. .TP \fB\-h\fR, \fB\-\-help\fR print help page diff --git a/src/setup/gnunet-setup.c b/src/setup/gnunet-setup.c index 2b95f4d4..77734ecc 100644 --- a/src/setup/gnunet-setup.c +++ b/src/setup/gnunet-setup.c @@ -385,7 +385,7 @@ GNUNET_SETUP_quit_cb (GObject *object, gpointer user_data) #ifndef MINGW /** - * Try elevating user priviledges to run as user 'gnunet' or 'root'. + * Try elevating user privileges to run as user 'gnunet' or 'root'. * * @param username user gnunet-setup should be run as * @return #GNUNET_OK on success @@ -538,7 +538,7 @@ main (int argc, char *const *argv) #ifndef MINGW GNUNET_GETOPT_option_flag ( 'e', - "elevate-priviledges", + "elevate-privileges", gettext_noop ( "run as user 'gnunet', if necessary by executing gksu to elevate rights"), &do_gksu), -- 2.23.0