From e734ecc1334b00532a71641a7a571acc07e8354f Mon Sep 17 00:00:00 2001 From: =?utf8?q?Ji=C5=99=C3=AD=20=C5=A0kr=C3=A1bal?= Date: Fri, 23 Sep 2005 11:42:03 +0000 Subject: [PATCH] - lb_dump_exporter usage added --- org.glite.jp.client/doc/README.jpimporter | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/org.glite.jp.client/doc/README.jpimporter b/org.glite.jp.client/doc/README.jpimporter index 750a314..74f5ec2 100644 --- 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. - +lb_dump_exporter usage: lt-lb_dump_exporter [option] + -h, --help Shows this screen. + -d, --dump Dump file location. + File generated by the glite-lb-purge + -s, --store New dump files storage. + Directory, where to store all dump files + -j, --jpps Target JPPS. + jpps where should the file be uploaded + -m, --lbmaildir 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 -- 1.8.2.3