From 91ee93fc26df5064d7c64bdaa4838669d23cdf53 Mon Sep 17 00:00:00 2001
From: Arun Isaac
Date: Wed, 15 Jun 2022 14:56:13 +0530
Subject: virtuoso: Document hack to get PID of container shepherd.

* topics/systems/virtuoso.gmi (Running virtuoso)[Running virtuoso in a
guix system container]: Document hack to get PID of container
shepherd.
---
 topics/systems/virtuoso.gmi | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

(limited to 'topics/systems/virtuoso.gmi')

diff --git a/topics/systems/virtuoso.gmi b/topics/systems/virtuoso.gmi
index 7ff6b04..b48fbef 100644
--- a/topics/systems/virtuoso.gmi
+++ b/topics/systems/virtuoso.gmi
@@ -39,10 +39,13 @@ sudo $(guix system container --network --share=/tmp/virtuoso-state=/var/lib/virt
 ```
 
 When running the above command, you will be given the container's PID. Should you want to inspect the container, you can run:
-
 ```
 sudo nsenter -at PID /run/current-system/profile/bin/bash
 ```
+If you have only one shepherd process running on your system, you may use the following quick hack to get the PID.
+```
+sudo nsenter -at $(pgrep shepherd) /run/current-system/profile/bin/bash
+```
 
 Also, in this set-up, note that the conductor web interface is not supported in the GUIX Service that's part of guix-bioinformatics. It isn't required for using virtuoso as a SPARQL server and only adds to the confusion.
 
-- 
cgit v1.2.3