From f71b5d2df5ca5ef94dc8da9274b6c19026162968 Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Mon, 7 Oct 2024 15:05:07 +0200
Subject: [PATCH] Fix link
---
doc.zih.tu-dresden.de/docs/data_lifecycle/overview.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc.zih.tu-dresden.de/docs/data_lifecycle/overview.md b/doc.zih.tu-dresden.de/docs/data_lifecycle/overview.md
index e20e5a9ef..2985a05cb 100644
--- a/doc.zih.tu-dresden.de/docs/data_lifecycle/overview.md
+++ b/doc.zih.tu-dresden.de/docs/data_lifecycle/overview.md
@@ -40,8 +40,8 @@ filesystems.
[`walrus` filesystem](working.md) can be used.
* If your batch job needs a directory for temporary data then node-local storage (`/tmp`) is
a good choice. The data will be deleted when the job has finished. The subsection
- [Node-Local Storage in Jobs](/slurm/#node-local-storage-in-jobs) holds valuable information on
- this topic.
+ [Node-Local Storage in Jobs](../jobs_and_resources/slurm.md#node-local-storage-in-jobs) holds
+ valuable information on this topic.
Keep in mind that every workspace has a storage duration. Thus, be careful with the expire date
otherwise it could vanish. The core data of your project should be [backed up](#backup) and the most
--
GitLab