From f9e1a6fb2513510a99738af31f7681f9f3e71695 Mon Sep 17 00:00:00 2001 From: Louwrentius Date: Fri, 6 Feb 2009 21:08:55 +0000 Subject: [PATCH] Edited wiki page through web user interface. --- wiki/DistributedPPSS.wiki | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/wiki/DistributedPPSS.wiki b/wiki/DistributedPPSS.wiki index 84fe596..24c9a66 100644 --- a/wiki/DistributedPPSS.wiki +++ b/wiki/DistributedPPSS.wiki @@ -32,6 +32,10 @@ If a larger number of nodes are used, say more than five to ten, it will be a ha The easiest solution that comes to mind is to use a central configuration or instruction file on the central server. Nodes will be able to access this file, read its contents and act accordingly. +== Node status == + +If a larger number of nodes are used, it would be nice if some simple overview could be generated about the current status of nodes and the overal progress of the entire process. + == Locking of items through SSH == According to many sources on the Internet, the only reliable solution to *atomic* locking is to use the 'mkdir' command to create a file. The fun thing is that this is also true if 'mkdir' is executed through SSH.