Difference between revisions of "SUSE Manager/Spacecmd"

From MicroFocusInternationalWiki
Jump to: navigation, search
(Created page with "# spacecmd is acting weird When running 'spacecmd', it does not accept commands or options: > susemanager:~ # spacecmd user_create -u sauron -l lotr -e sauron@dark-tower...")
 
m
Line 1: Line 1:
# spacecmd is acting weird
+
== spacecmd is acting weird ==
  
When running 'spacecmd', it does not accept commands or options:
+
For example, when running 'spacecmd', it does not seem to accept commands or options:
  
    > susemanager:~ # spacecmd user_create -u sauron -l lotr -e sauron@dark-tower.mordor --pam
+
spacecmd user_create -u tux -l lotr -e tux@example.com --pam
    Usage: spacecmd [options] [command]
+
Usage: spacecmd [options] [command]
  
  
When running spacecmd non-interactively, you must take care to escape arguments passed to the spacecmd functions.  This involves putting a '--' before the command starts so that the arguments to the function are not treated as global arguments to spacecmd.  You must also escape any quotes that you pass to the functions so that the shell does not interpret them.
+
When running spacecmd non-interactively, you must take care to escape arguments passed to the spacecmd functions.  This involves putting '--' before the command starts so that the arguments to the function are not treated as global arguments to spacecmd.  You must also escape any quotes that you pass to the functions so that the shell does not interpret them.
  
 
Example:
 
Example:
  
    spacecmd -s server1 -- softwarechannel_create -n \'My Channel\' -l channel1 -a x86_64
+
spacecmd -s server1 -- softwarechannel_create -n \'My Channel\' -l channel1 -a x86_64

Revision as of 11:47, 22 October 2013

spacecmd is acting weird

For example, when running 'spacecmd', it does not seem to accept commands or options:

spacecmd user_create -u tux -l lotr -e tux@example.com --pam
Usage: spacecmd [options] [command]


When running spacecmd non-interactively, you must take care to escape arguments passed to the spacecmd functions. This involves putting '--' before the command starts so that the arguments to the function are not treated as global arguments to spacecmd. You must also escape any quotes that you pass to the functions so that the shell does not interpret them.

Example:

spacecmd -s server1 -- softwarechannel_create -n \'My Channel\' -l channel1 -a x86_64