Embedded scripts run from Windows fail on Unix
Reported by Dave Tauzell | August 5th, 2011 @ 12:29 PM
Given:
that you have Rundeck running on Windows
When:
you create a job with an "inline script" step
and the script is like:
#!/bin/bash
echo hello
Then:
The script will fail because the script that is copied over has \r\n linefeeds
The error will be something like:
bash: /tmp/1312570144936-carver-dispatch-script.sh: /bin/bash^M: bad interpreter: No such file or directory
Comments and changes to this ticket
-
liam smith July 31st, 2024 @ 05:15 AM
Embedded scripts designed for Windows often fail on Unix systems due to differences in file formats, path separators, and line endings. dish internet and cable packages Windows scripts typically use CRLF (Carriage Return + Line Feed) for line breaks, while Unix systems use LF (Line Feed) only. Additionally, Windows paths use backslashes, whereas Unix paths use forward slashes. To ensure compatibility, convert line endings and adjust paths accordingly before executing scripts on Unix.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
(DEPRECATED) Please use github issues for issue tracking at http://github.com/dtolabs/rundeck/issues
Alex-SF
Dave Tauzell
Greg Schueler