Running-the-jobs/Connect-on-a-running-job's-node.md

@@ -13,31 +13,9 @@ Authentication failed.
 
 But what if your own job is running on a compute node ? then you have a legitimate motive to connect to that job (to run a [top](https://en.wikipedia.org/wiki/Top_(software)), [gstack](https://linux.die.net/man/1/gstack) or [link](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/developer_guide/debugging-running-application) a debug session on you running process) and `slurm` has been configured to allow 
 
-## Real example:
-**Go to Licallo:**
+## With a running job
 
-```
-ctchiling@pcp-ctchiling:~$ ssh licallo
-ctchiling@licallo's password: 
-Last login: Thu Feb 18 14:02:31 2021 from 10.254.1.241
-                                                 _ _            
-                                     _ __   ___ | | |_   ___  __
-                                    | '_ \ / _ \| | | | | \ \/ /
-                                    | |_) | (_) | | | |_| |>  < 
-                                    | .__/ \___/|_|_|\__,_/_/\_\
-                                    |_|                         
-
-Welcome to CentOS Linux 7 (Core) (GNU/Linux 3.10.0-1127.el7.x86_64 x86_64)
-
-You can get several information on: https://pollux/
-
-System information as of Thu Feb 18 16:59:01 CET 2021
-
-System Uptime:	99 days 20 hours 37 min 31 sec
-System Load:  	0.03, 0.03, 0.05
-Processes:    	515
-Local Users:  	14
-```
+For this example, we consider a [dummy job](`SLURM/running/sleep.slurm`) that just sleep for 5 minutes:
 
 **Then, go SLURM**
 ```