From 2555bd5ac6c975b8809d36ef90daaa8f71a8e0ba Mon Sep 17 00:00:00 2001
From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
Date: Tue, 5 Jul 2016 21:47:28 +0200
Subject: documentation: Move README-VALGRIND out of doc/_attic_/ folder to
 doc/nxproxy/.

---
 .../nxproxy_README-VALGRIND                        | 39 ----------------------
 doc/nxproxy/README-VALGRIND                        | 39 ++++++++++++++++++++++
 2 files changed, 39 insertions(+), 39 deletions(-)
 delete mode 100644 doc/_attic_/NoMachine_documentation_files/nxproxy_README-VALGRIND
 create mode 100644 doc/nxproxy/README-VALGRIND

(limited to 'doc')

diff --git a/doc/_attic_/NoMachine_documentation_files/nxproxy_README-VALGRIND b/doc/_attic_/NoMachine_documentation_files/nxproxy_README-VALGRIND
deleted file mode 100644
index ce4d513a4..000000000
--- a/doc/_attic_/NoMachine_documentation_files/nxproxy_README-VALGRIND
+++ /dev/null
@@ -1,39 +0,0 @@
-README-VALGRIND
----------------
-
-You can run nxproxy (and nxcomp) under the supervision of valgrind
-(a very good memory debugger) by wrapping nxproxy in the following
-script:
-
-<snip>
-#!/bin/bash
-
-# Enable core dumps.
-
-ulimit -c unlimited
-
-# Set this to directory where nxproxy is located.
-
-NXPROXY_DIR=~/NX/nxproxy
-
-# Set this to directory where valgrind is located.
-
-VALGRIND_DIR=/usr/local/bin
-
-exec ${VALGRIND_DIR}/valgrind -v --leak-check=yes --leak-resolution=high \
-                              --show-reachable=yes --show-reachable=yes \
-                              --suppressions=${NXPROXY_DIR}/nxproxy.supp \
-                              --num-callers=16 --logfile-fd=2 \
-\
-${NXPROXY_DIR}/nxproxy $1 $2 $3 $4 $5 $6 $7 $8 $9
-<snip>
-
-Run the following commands on your shell, right in the place where
-the nxproxy executable is to be placed in your setup:
-
-$ cat >nxproxy
-<copy paste the previous lines here>
-$ chmod a+x nxproxy
-
-Output of valgrind will go on stderr, that is in session file, if
-run in NX environment.
diff --git a/doc/nxproxy/README-VALGRIND b/doc/nxproxy/README-VALGRIND
new file mode 100644
index 000000000..ce4d513a4
--- /dev/null
+++ b/doc/nxproxy/README-VALGRIND
@@ -0,0 +1,39 @@
+README-VALGRIND
+---------------
+
+You can run nxproxy (and nxcomp) under the supervision of valgrind
+(a very good memory debugger) by wrapping nxproxy in the following
+script:
+
+<snip>
+#!/bin/bash
+
+# Enable core dumps.
+
+ulimit -c unlimited
+
+# Set this to directory where nxproxy is located.
+
+NXPROXY_DIR=~/NX/nxproxy
+
+# Set this to directory where valgrind is located.
+
+VALGRIND_DIR=/usr/local/bin
+
+exec ${VALGRIND_DIR}/valgrind -v --leak-check=yes --leak-resolution=high \
+                              --show-reachable=yes --show-reachable=yes \
+                              --suppressions=${NXPROXY_DIR}/nxproxy.supp \
+                              --num-callers=16 --logfile-fd=2 \
+\
+${NXPROXY_DIR}/nxproxy $1 $2 $3 $4 $5 $6 $7 $8 $9
+<snip>
+
+Run the following commands on your shell, right in the place where
+the nxproxy executable is to be placed in your setup:
+
+$ cat >nxproxy
+<copy paste the previous lines here>
+$ chmod a+x nxproxy
+
+Output of valgrind will go on stderr, that is in session file, if
+run in NX environment.
-- 
cgit v1.2.3