# Trouble with raw module and /bin/sh -c

**URL:** <https://forum.ansible.com/t/trouble-with-raw-module-and-bin-sh-c/12188>\
**Category:** Ansible Project\
**Created:** [January 8, 2013, 3:59pm UTC](https://forum.ansible.com/t/trouble-with-raw-module-and-bin-sh-c/12188 "2013-01-08T15:59:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Philipp\_Grau](https://avatars.discourse-cdn.com/v4/letter/p/74df32/32.png) [@Philipp\_Grau](https://forum.ansible.com/u/Philipp_Grau)\
**Post date:** [January 8, 2013, 3:59pm UTC](https://forum.ansible.com/t/trouble-with-raw-module-and-bin-sh-c/12188/1 "2013-01-08T15:59:23Z")

</div>

Hello,

I tried to collect some data from bladecenter equipment. The current access  
method is SSH with password (Changing is possible but a lengthy and  
error-prone task, which I like to avoid, and ansible -k is so handy)

The problem is that ansible uses "/bin/sh -c 'remote command'", and since  
the remotes are no unix maschines it fails.

I saw this problem already in the irc channel, but there was no solution.

Should there be an option to the raw module? What can I/we do?

Kind regards,

Philipp

---

<div class="post-metadata">

**Author:** ![Dag\_Wieers](https://avatars.discourse-cdn.com/v4/letter/d/45deac/32.png) [@Dag\_Wieers](https://forum.ansible.com/u/Dag_Wieers)\
**Post date:** [January 9, 2013, 1:00pm UTC](https://forum.ansible.com/t/trouble-with-raw-module-and-bin-sh-c/12188/2 "2013-01-09T13:00:32Z")

</div>

There have been some changes to the raw module recently. One allows to provide a different executable= to be used as a shell. Another change does not use a shell by default, but it can still be provided on the command line using e.g. executable=/bin/sh

You need to use the latest devel branch in order to use these changes.

We'd like to hear if this works for you.