Just checked; if you're SSHing in as a non-root user
(vagrant here)
and running the plays via become: then you'll see the sudo messages
in /var/log/secure (on CentOS6; YMMV for other distros) and the
task messages in /var/log/messages.
(the playbook just checks the mysqld service is running, essen
Sudoing to run Ansible on the control machine won't show up in the
target server logs.
If ansible sudos on the targets (i.e. you have become: yes in the
plays) that should show up.
On 21 June 2017 at 15:56, Steve Zimmerman wrote:
> Hello,
> I have an audit/security request to include the us
Hello,
I have an audit/security request to include the user id in the
messages log for commands issued against a linux server. To illustrate, the
commands are issued with as sudo:
# sudo ansible ---
results in /var/log/messages:
Jun 19 00:01:13 usildng-ps-03 ansible-command: Invoked with
