*Steve,*
yup, I found that later on as well - was not used to read source code to
get 'documentation' - but am learning :-)
*Brian,*
ok, so what is the solution?
I need to run 'sesu -' otherwise the commands will not be executed properly
since they require the environment to be setup as per the
ansible avoids doing full logins on purpose to avoid things like that,
so adding - to the options will break.
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it,
On 08/31/2015 06:41 AM, damasek.sh...@gmail.com wrote:
> Thanks Brian - I didn't know that's possible (it is not documented in the
> default config file)
You are right on that one, however the documentation does hint to constants.py
in the repo so with that handy:
~/work/ansible/ansible-proj
Thanks Brian - I didn't know that's possible (it is not documented in the
default config file) - yes, that actually gets me much closer - THANK YOU
:-)
However I am now getting another error since ansible does not seem to be
able to ignore the standard 'login information messages' during the su
Hi Brian,
I tried to look for it but not sure where to find that - can you please
point me to the right place?
Thank you,
M.
On Friday, August 28, 2015 at 12:19:11 AM UTC+2, Brian Coca wrote:
>
> try setting ansible_su_exe in the inventory
>
>
>
> --
> Brian Coca
>
--
You received this mes
try setting ansible_su_exe in the inventory
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-project+unsubscr...@googlegroups.com.
To
Was there any update on adding ability to use sesu? Note that in our case
sesu does NOT prompt for the 'to become' user. Here is how we use it:
1) login under my personal user id
2) run "sesu - "
3) ... it will NOT ask for any password and will directly log me under the
to_become_user_id
FYI he
excellent!
On Tue, Sep 9, 2014 at 3:06 AM, Edgars wrote:
> Well, sesu supports "-" flag and "-c" flag just like su. Those two are
> most important I guess. The main difference is that su requires root
> password when you switch to root while sesu requires user password, just
> like sudo. But I
Well, sesu supports "-" flag and "-c" flag just like su. Those two are most
important I guess. The main difference is that su requires root password
when you switch to root while sesu requires user password, just like sudo.
But I don't think that this should be problem.
Edgars
pirmdiena, 2014.
I think so. (Would be open to contributions, but we could also do it
ourself if needed).
Is it mostly flag compatible?
The one thing I want to fix with sudo_exe is it should be settable per
inventory host, so we'll probably do that at the same time too, and leave
the ansible.cfg setting for a de
Hi
I see that Ansible has sudo_exe feature for alternative sudo
implementations. Would it be possible to implement also su_exe for
alternative su implementations? In particular I am interested in CA
AccessControl sesu
utility:
https://support.ca.com/cadocs/0/CA%20Access%20Control%2012%205%205
11 matches
Mail list logo
