From 348e1af37ecfd3dca895c095a4a3de2d46b8c534 Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Thu, 25 Oct 2007 15:55:32 -0400 Subject: Docs cleanup/fix --- docs/func.pod | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) (limited to 'docs') diff --git a/docs/func.pod b/docs/func.pod index c95788f..bc8518e 100644 --- a/docs/func.pod +++ b/docs/func.pod @@ -48,6 +48,16 @@ Once you have the name of a module you want to run, use call to invoke it: func target.example.org call modulename methodname +=head1 OUTPUT FORMATS + +The "call" command by default outputs data using a "pretty printer". Other +display options include --raw, --json, and --xmlrpc, which may be more +desirable if you are running func inside another script or prefer to read +those display formats. + +Example: func "*" call --json service inventory + + =head1 HELPER MODULES In addition to "call", there are other modules that make control of remote @@ -78,13 +88,6 @@ func "*.example.org" copyfile --file=/tmp/foo --remotepath=/tmp/foo While these helper modules will grow over time, usage of "call" syntax directly is fine also. See the Wiki for more examples as they evolve. -=head1 OUTPUT COMMANDS - -The "call" command by default outputs data using a "pretty printer". Other -display options include --raw, --json, and --xmlrpc, which may be more -desirable if you are running func inside another script or prefer to read -those display formats. - =head1 --verbose Use this flag to output extra information from func while it is running. -- cgit