??????????????
Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 173

Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 174

Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 175

Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 176

Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 177

Warning: Cannot modify header information - headers already sent by (output started at /home/mybf1/public_html/mentol.bf1.my/SS1.php:4) in /home/mybf1/public_html/mentol.bf1.my/SS1.php on line 178
ó àUdac@`szddlmZmZmZeZdZdZdZddl Z ddl m Z ddl m Z de fd „ƒYZdS( i(tabsolute_importtdivisiontprint_functions¥ lookup: pipe author: Daniel Hokka Zakrisson version_added: "0.9" short_description: read output from a command description: - Run a command and return the output. options: _terms: description: command(s) to run. required: True notes: - Like all lookups this runs on the Ansible controller and is unaffected by other keywords, such as become, so if you need to different permissions you must change the command or run Ansible as another user. - Alternatively you can use a shell/command task that runs against localhost and registers the result. - Pipe lookup internally invokes Popen with shell=True (this is required and intentional). This type of invocation is considered as security issue if appropriate care is not taken to sanitize any user provided or variable input. It is strongly recommended to pass user input or variable input via quote filter before using with pipe lookup. See example section for this. Read more about this L(Bandit B602 docs,https://bandit.readthedocs.io/en/latest/plugins/b602_subprocess_popen_with_shell_equals_true.html) sü - name: raw result of running date command" debug: msg: "{{ lookup('pipe', 'date') }}" - name: Always use quote filter to make sure your variables are safe to use with shell debug: msg: "{{ lookup('pipe', 'getent ' + myuser | quote ) }}" s9 _string: description: - stdout from command N(t AnsibleError(t LookupBaset LookupModulecB`seZd„ZRS(c K`s¶g}x©|D]¡}t|ƒ}tj|d|jjƒdtdtjdtjƒ}|jƒ\}}|jdkr•|j |j dƒj ƒƒq t d||jfƒ‚q W|S(Ntcwdtshelltstdintstdoutisutf-8s"lookup_plugin.pipe(%s) returned %d( tstrt subprocesstPopent_loadert get_basedirtTruetPIPEt communicatet returncodetappendtdecodetrstripR( tselfttermst variablestkwargstretttermtpR tstderr((s?/usr/lib/python2.7/site-packages/ansible/plugins/lookup/pipe.pytrun5s 6(t__name__t __module__R(((s?/usr/lib/python2.7/site-packages/ansible/plugins/lookup/pipe.pyR3s(t __future__RRRttypet __metaclass__t DOCUMENTATIONtEXAMPLEStRETURNR tansible.errorsRtansible.plugins.lookupRR(((s?/usr/lib/python2.7/site-packages/ansible/plugins/lookup/pipe.pyts