sneak/ppss
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Edited wiki page through web user interface.

Browse Source
This commit is contained in:
Louwrentius 2010-03-08 08:12:42 +00:00
parent 6743b7f1a1
commit 4d4e7a5a6b
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
wiki/Manual2.wiki
View File

@ -339,7 +339,7 @@ All variables specified when generating a configuration script can be used withi
Once SSH access is setup and the configuration file is generated, PPSS can be deployed to the nodes. This is very simple, as this example demonstrates:
`./ppss.sh deploy -C config.cfg
`./ppss deploy -C config.cfg
During the phase when we generated the configuration file, a nodes file was specified. Thus PPSS knows, just by reading this configuration file, which file contains a list of nodes.
@ -368,7 +368,7 @@ Deployment of PPSS is executed in parallel for each host.
Just as simple as deploying PPSS, PPSS is started on all nodes.
`./ppss.sh start -C config`
`./ppss start -C config`
{{{
mrt 12 22:21:17: INFO - ---------------------------------------------------------
@ -384,9 +384,9 @@ mrt 12 22:21:20: INFO - Starting PPSS on node 10.0.0.31.
To stop, pause or continue processing on all nodes, use the following commands:
`./ppss.sh stop -C config.cfg`
`./ppss.sh pause -C config.cfg`
`./ppss.sh continue -C config.cfg`
`./ppss stop -C config.cfg`
`./ppss pause -C config.cfg`
`./ppss continue -C config.cfg`
Please note that nodes will continue processing the current item they are working on, they just stop processing new items if stop or pause is selected.