From cfe6a4632abb1c6ded8bad7389e2ec76725d1b92 Mon Sep 17 00:00:00 2001
From: Maksim Melnik Storetvedt <maksim.melnik.storetvedt@cern.ch>
Date: Thu, 19 Nov 2020 15:29:28 +0000
Subject: [PATCH] Update ce_guide.md
---
docs/site/ce_guide.md | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/docs/site/ce_guide.md b/docs/site/ce_guide.md
index 25f433e..9e5579e 100644
--- a/docs/site/ce_guide.md
+++ b/docs/site/ce_guide.md
@@ -22,11 +22,10 @@ This approach only requires CVMFS and a valid Grid certificate or a user/host to
2. Load the JAliEn environment:
```console
+ #If not in path, can be found at `/cvmfs/alice.cern.ch/bin/alienv`.
~$ alienv enter JAliEn
```
-Note that it is assumed here that `alienv` is already in path. If not, it can be found at `/cvmfs/alice.cern.ch/bin/alienv`.
-
3. Run the CE:
```console
@@ -130,3 +129,15 @@ A trivial solution can be to extend the above wrapper script with a restarter as
sleep 1800
done
```
+
+## FAQ
+
+**What about logs?**
+
+The JAliEn CE log directory is defined in LDAP, the same way as for legacy AliEn. A common directory used is ```~/ALICE/alien-logs```.
+
+**What about updates?**
+
+When using option 1 (CE in CVMFS), the CE can be updated by simply reloading the CE and alienv, activating the latest tag. For option 2 (CE from git), the latest version can be obtained by doing a ```git pull``` and ```compile.sh all```, before restarting.
+
+No action is needed for the JobAgents, as these are always started using the latest tag in CVMFS.
--
GitLab