diff options
| author | Rich Megginson <rmeggins@redhat.com> | 2012-08-20 09:01:16 -0600 |
|---|---|---|
| committer | Rich Megginson <rmeggins@redhat.com> | 2012-08-20 09:01:16 -0600 |
| commit | 4fbdee32a7b73bfd1b70b5b1c080036498157e1e (patch) | |
| tree | 76ec0a063700f9698ed06b4ae16dd3ee98988cc8 /setupscript4.cmd.in | |
| parent | 7c079e3402ee5cad6d12c972ae83b040b4435a2a (diff) | |
| download | auto-win-vm-ad-4fbdee32a7b73bfd1b70b5b1c080036498157e1e.tar.gz auto-win-vm-ad-4fbdee32a7b73bfd1b70b5b1c080036498157e1e.tar.xz auto-win-vm-ad-4fbdee32a7b73bfd1b70b5b1c080036498157e1e.zip | |
use $SUDOCMD to run vm commands - add user SetupComplete as last step
One of the problems with make-ad-vm.sh is that there was no way to know
when it was complete. setupscript99.cmd will create an AD user called
SetupComplete as the very last step. When this user is present, the
setup process is finished. The make-ad-vm.sh script will delete this
user entry.
Some of the virsh and vm commands can only be run by root. These commands
are now prefixed with $SUDOCMD. If you are running the script as a non-root
user, and you have sudo setup to allow that user to run the commands, you
can use
SUDOCMD=sudo ..othervars.. make-ad-vm.sh ....
Otherwise, if you are running as root, just leave SUDOCMD blank.
Diffstat (limited to 'setupscript4.cmd.in')
0 files changed, 0 insertions, 0 deletions