gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[taler-docs] branch master updated: SystemD instructions


From: gnunet
Subject: [taler-docs] branch master updated: SystemD instructions
Date: Tue, 02 Feb 2021 16:31:53 +0100

This is an automated email from the git hooks/post-receive script.

ms pushed a commit to branch master
in repository docs.

The following commit(s) were added to refs/heads/master by this push:
     new 8d7eaa6  SystemD instructions
8d7eaa6 is described below

commit 8d7eaa6a4da8cb8fe1a26ca063d5100862b2e588
Author: ms <ms@taler.net>
AuthorDate: Tue Feb 2 16:31:50 2021 +0100

    SystemD instructions
---
 libeufin/nexus-tutorial.rst | 39 +++++++++++++++++++++++++++++++++++++++
 1 file changed, 39 insertions(+)

diff --git a/libeufin/nexus-tutorial.rst b/libeufin/nexus-tutorial.rst
index 07ef218..2a97b2c 100644
--- a/libeufin/nexus-tutorial.rst
+++ b/libeufin/nexus-tutorial.rst
@@ -38,6 +38,45 @@ To install LibEuFin, you can now simply run:
 
    # apt install libeufin
 
+Administration via SystemD
+--------------------------
+
+After the Debian installation, the installed unit files
+should be listed by the following command:
+
+.. code-block:: console
+
+   # systemctl list-unit-files | egrep '(nexus|sandbox)'
+
+Both ``nexus.service`` and ``sandbox.service`` should appear.
+
+At this point, the services can be started on boot:
+
+.. code-block:: console
+
+   # systemctl enable nexus # use 'disable' to rollback
+   # systemctl enable sandbox
+
+Or just manually:
+
+.. code-block:: console
+
+   # systemctl start nexus # use 'stop' to terminate.
+   # systemctl start sandbox
+
+Generally, the following command should inform the
+user about the status of the running / terminated service:
+
+.. code-block:: console
+
+   # systemctl status nexus
+
+For more diagnostics, use:
+
+.. code-block:: console
+
+   # journalctl -u nexus
+
 Run-time dependencies
 ---------------------
 

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]