From d79808ee4223eabc50ed189e1941ff4edaa8f6ae Mon Sep 17 00:00:00 2001 From: Louwrentius Date: Sat, 10 Jan 2009 15:13:29 +0000 Subject: [PATCH] Edited wiki page through web user interface. --- wiki/DistributedPPSS.wiki | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/wiki/DistributedPPSS.wiki b/wiki/DistributedPPSS.wiki index 5a102ae..ab6a2b7 100644 --- a/wiki/DistributedPPSS.wiki +++ b/wiki/DistributedPPSS.wiki @@ -9,10 +9,9 @@ The goal is to make PPSS distributed. So a large number of host can be used to p The most simple and clean solution to make PPSS is the use of SSH to lock items. If items are files that need to be processed, they can be accessed in two ways: - * using a network file system such as NFS or SMB or other. + * using a network file system such as NFS or SMB or other. The -d option must point to the mountpoint of this share. * using scp within scripts to (securely) copy items (files) to the local host and copy the processed items back to the server. A lock directory must be created that will contain all lock files (lock directories) for items that must be processed. A limitation may be the maximum amount of (sub)directories within a single directory that a filesystem can handle. -To determine if an item has been processed, PPSS checks if a log file for an item is present in the directory job_log. This job_log directory should be shared with all hosts that are running PPSS. - +To determine if an item has been processed, PPSS checks if a log file for an item is present in the directory job_log. This job_log directory should be shared with all hosts that are running PPSS. \ No newline at end of file