Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix typo in --ask-sudo-pass reference within playbook_intro doc #11060

Merged
merged 1 commit into from
May 25, 2015
Merged

fix typo in --ask-sudo-pass reference within playbook_intro doc #11060

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion docsite/rst/playbooks_intro.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -186,7 +186,7 @@ You can also use other privilege escalation methods, like su::
become_method: su

If you need to specify a password to sudo, run `ansible-playbook` with ``--ask-become-pass`` or
when using the old sudo syntax ``--ask-sudo--pass`` (`-K`). If you run a become playbook and the
when using the old sudo syntax ``--ask-sudo-pass`` (`-K`). If you run a become playbook and the
playbook seems to hang, it's probably stuck at the privilege escalation prompt.
Just `Control-C` to kill it and run it again adding the appropriate password.

Expand Down