- lb_dump_exporter usage added

diff --git a/org.glite.jp.client/doc/README.jpimporter b/org.glite.jp.client/doc/README.jpimporter
index 750a314..74f5ec2 100644 (file)
--- a/org.glite.jp.client/doc/README.jpimporter
+++ b/org.glite.jp.client/doc/README.jpimporter
@@ -23,7 +23,17 @@ For LB dumps, there is another utility, which parses common LB dump files
 message describing the location, destination etc. to local directory. This
 message directory should be obviously monitored by the jpimporter again.
 
-</TODO lb_dump_exporter describtion />
+lb_dump_exporter usage: lt-lb_dump_exporter [option]
+        -h, --help              Shows this screen.
+        -d, --dump <file>       Dump file location.
+                                File generated by the glite-lb-purge
+        -s, --store <prefix>    New dump files storage.
+                                Directory, where to store all dump files
+        -j, --jpps <host:port>  Target JPPS.
+                                jpps where should the file be uploaded
+        -m, --lbmaildir <path>  LB maildir path.
+                                Directory, where should be stored the message
+                                describing the file upload (read by jpimporter)
 
 For the sandbox files, you should use the JP client API to create messages for
 jpimporter. The function glite_jpimporter_upload_files() do the job. It takes