salt/scripts
Sergey Kizunov 57fba60eda Make extensionless scripts runable in Windows
Previously, to make these run on Windows, I added the '.py'
extension. For example 'salt-master' => 'salt-master.py'

If this wasn't done, you would get an exception that looks like this
when spawning an addition process:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
    File "C:\salt\bin\lib\multiprocessing\forking.py",
    line 380, in main
        prepare(preparation_data)
          File "C:\salt\bin\lib\multiprocessing\forking.py",
          line 489, in prepare
              file, path_name, etc = imp.find_module(main_name, dirs)
              ImportError: No module named salt-master

Instead of adding the '.py' extension, I found another work-around that
seems to avoid the issue. The details are described in the file comments.

Signed-off-by: Sergey Kizunov <sergey.kizunov@ni.com>
2015-05-15 20:04:55 -05:00
..
salt Updated hashbangs with /usr/bin/env for virtual environment installs 2013-01-03 11:36:51 +02:00
salt-api factorize call 2014-11-11 17:43:05 +01:00
salt-call Updated hashbangs with /usr/bin/env for virtual environment installs 2013-01-03 11:36:51 +02:00
salt-cloud Modernize the salt-cloud script 2013-11-08 14:11:27 -07:00
salt-cp Updated hashbangs with /usr/bin/env for virtual environment installs 2013-01-03 11:36:51 +02:00
salt-key Updated hashbangs with /usr/bin/env for virtual environment installs 2013-01-03 11:36:51 +02:00
salt-master Make extensionless scripts runable in Windows 2015-05-15 20:04:55 -05:00
salt-minion Make extensionless scripts runable in Windows 2015-05-15 20:04:55 -05:00
salt-run Updated hashbangs with /usr/bin/env for virtual environment installs 2013-01-03 11:36:51 +02:00
salt-ssh Add salt-ssh script 2013-07-01 15:48:23 -06:00
salt-syndic Updated hashbangs with /usr/bin/env for virtual environment installs 2013-01-03 11:36:51 +02:00
salt-unity Make extensionless scripts runable in Windows 2015-05-15 20:04:55 -05:00