Problems to run shell scripts in terminal

Hey mates,
I'm not very experienced in writing shell scripts. However, I received a few shell scripts I wanted to execute. I used following command:
chmod u+x model.sh
I did not received any error message so that I think that this command works. Afterwards, I wanted to run these file with:
./model.sh
However, it doesn't work, I receive an error message:
-bash: ./model.sh: /bin/sh^M: bad interpreter: No such file or directory
If I choose another shell script of my colleague I can run it and it works properly. What's the problem?
I use in all shell scripts the same syntax starting with
"! /bin/sh
Thus, I don't see the reason why the first script isn't running while the second one is fine.
Help appreciated!
cheers,
Thomas

Unix and Terminal questions are best asked in the Mac OS X Technologies > Unix Forum
<http://discussions.apple.com/forum.jspa?forumID=735>
As jsd2 has pointed out, you CANNOT have Windows <CR><LF> line terminators in your file (aka ^M^J). Just about every Unix shell will choke on the <CR>
We run into this problem all the time with users moving Unix shell scripts through a Windows system and having Windows convert the <LF> terminated Unix files into Windows <CR><LF> files, and then either use them in a Windows Cygwin environment (where they "Barf"), or move them back to a Unix system with the <CR><LF> line terminations still in the scripts, and they "Barf".
You can look at the contents of your scripts using the following command
cat -v script.name
Any ^M characters found at the end of lines will be part of <CR><LF> Windows line terminators.
You can use the following command to remove the <CR> from those files
tr -d '
' <script.name >new.name
chmod +x new.name
If you wish to pursue this further, I would suggest using the Mac OS X Technologies > Unix Forum
<http://discussions.apple.com/forum.jspa?forumID=735>

Similar Messages

Running shell script from terminal

If I run this shell script from the terminal it plays the sound though my external speakers;
volume="/Volumes/8GIGSTICK"
if mount|grep $volume; then
afplay -d /System/Library/Sounds/insert.wav
rsync -a /volumes/8GIGSTICK/documents /Users/mcp/Documents/Microsoft\ User\ Data/
else
say not mounted
fi
If I have launchd run it when the volumes is mounted it only plays the sound through the internal computer speaker.
Anyone know why and how I can fix it?

It's probably because your launchd job isn't running in the Aqua context and therefore doesn't pick up your sound-output preferences. One way to overcome this would be to load the job as follows:
launchctl load -S Aqua -D user job_label
That's assuming you have a launchd property list at ~/Library/LaunchAgents/job_label.plist. To make the effect persist across login sessions, you would create a file ~/.launchd.conf with the contents
load -S Aqua -D user job_label

How to use "do shell script" when Terminal replies with a prompt?

Hey all,
I'm wondering how to properly use "do shell script" when Terminal replies with a question? In this example, I'm building a small tool in AppleScript that will auto-update the Android SDK via command line prompts. The problem is when I tell it to update all ("update sdk --no-ui"), I need to accept licence agreements before it continues, and the amount of licence agreements brought up is different every time.
So, basically, I'm wondering how to handle a case where "do shell script" encounters a case where Terminal would normally need a user's response to?
Thanks,
Behn

If it is variable number of prompts that is a problem. Look around hd and figure out how many prompts there will be. Ask around android forum for a bash solution. There are some test case apps that will let you put conditionals on output from running programs.
# traditional way. Pipe output to command.
do script "echo 'ok' | update sdk --no-u"
Here is the preferred way of getting administrator privileges.
It is easier to diagnose problems with debug information. I suggest adding log statements to your script to see what is going on. Here is an example.
    Author: rccharles
    For testing, run in the Script Editor.
      1) Click on the Event Log tab to see the output from the log statement
      2) Click on Run
    For running shell commands see:
    http://developer.apple.com/mac/library/technotes/tn2002/tn2065.html
on run
    -- Write a message into the event log.
    log " --- Starting on " & ((current date) as string) & " --- "
    -- debug lines
    set unixDesktopPath to POSIX path of "/System/Library/User Template/"
    log "unixDesktopPath = " & unixDesktopPath
    set quotedUnixDesktopPath to quoted form of unixDesktopPath
    log "quoted form is " & quotedUnixDesktopPath
    try
        set fromUnix to do shell script "sudo ls -l " & quotedUnixDesktopPath with administrator privileges
        display dialog "ls -l of " & quotedUnixDesktopPath & return & fromUnix
    on error errMsg
        log "ls -l error..." & errMsg
    end try
end run

Automator and "Run Shell Script" error

First, if I'm in the wrong place with this- sorry. Figured this was an OS kind-of thing.
I recently migrated to a new iMac ... I brought along an Automator script; I've been using it for years to perform a little rsync backup to an USB HDD. It's 'never' given me any problems ... until now!
"*Run Shell Script*" encountered an error .. but alas, the system log is devoid of messages ... and the verbose log I have running indicates that all the files are copied/backed-up ... I would love any input on this that might help me get back on the feet. .....
*Here's what my Shell Script Looks like:*
Shell Option: /bin/bash
Pass Input: to stdin
rm -dfr '/Volumes/Backup HD/*********'
rm -dfr '/Users/***********/Library/Logs/Profile_Backup.log'
rsync -rltv /Users/******** '/Volumes/Backup HD/' > /Users/*******/Library/Logs/Profile_Backup.log
(I'm sure there's way to only sync the changed stuff between backups ... but I've simply preferred the fresh copy approach).
*I do however note this in my logs when I open Automator:*
12/14/10 3:15:46 PM [0x0-0x42042].com.apple.automator.Backup[464] Application Stub: OpenScripting.framework - scripting addition "/Library/ScriptingAdditions/Adobe Unit Types.osax" declares no loadable handlers.

@Tony T1
Thanks, I'll certainly adjust the log file as suggested
In troubleshooting the problem I went the terminal route - and issued each command ... during the rsync process I was getting an error ... turns out when it was syncing the SyncServices folder it was encountering a copy of the keychain ... which had root permissions - naturally rsync was not able to copy the file (personally I have no idea why the keychain would be being sync'd with anything)!
I removed the file from the sync ... I'm still doing some "debugging" to correct the problem-
Again, thanks for the assist!

Perl's __END__ doesn't work under Automator's Run Shell Script action

Howdy,
I have a large embedded data file in my Perl source file using the _END_ token. It works great at the command line, but when I copy and paste my Perl code into the Run Shell Script code window and execute it, reading the special file handle DATA always returns 0 lines.
Help?
-Eric

Originally I was using $@ to parse a string and get the result pasted by the service. That was a while ago. There, I noticed that some Japanese characters were messed up. Basically all the kana characters that come with voicing markers like が-ga (instead of か-ka) etc. I did not have the time to pursue that issue though.
Then, last night, I found that a colleague of mine had tried to use $@ to feed to a local dictionary application called ding (http://ftp.tu-chemnitz.de/pub/Local/urz/ding/). His problem was with characters that had umlauts. After verifying how he wrote his action I remembered that I had similar issues with Japanese.
Basically his command was "/path/to/ding $@"
That's supposed to use the selected string as an argument to pass to ding, which will launch a Wish application where the string is used as the searched item.
From Terminal, that works a treat. But the exact same line in Automator (with input as argument, not as stdin) messed the composition and the resulting string was not recognized by ding as a match to what it was supposed to match.
So, I tried a few things to get to the core of the issue and found that a simple "echo [accented characters]" was enough to reproduce the difference in string handling between Automator and Terminal. That difference is also reproduced on a number of person's machines.
I have a number of services that basically revolve on "run shell script" actions and involve 3rd party application outputs, preference files etc. so it would not be convenient to show that to you.
I have sent a mail about this issue to the automator list yesterday too:
http://lists.apple.com/archives/Automator-users/2011/Jun/msg00004.html

How to prevent Automator's "run shell script" to create fully decomposed forms of my strings ?

I am using Automator's "run shell script" and I am seeing that it outputs fully decomposed forms of my strings.
For example, when I set the action to "echo été" in a service (with "Replace selected text" activated) and run that into a Textwrangler window, I'll get fully decomposed forms that Textwrangler won't understand. But when I simply type that command into Terminal, I get my string in composed form.
The problem is not the display issue, but the fact that if I want to run grep for example in "run shell script", I will not be able to find the proper strings since the forms are different.

Originally I was using $@ to parse a string and get the result pasted by the service. That was a while ago. There, I noticed that some Japanese characters were messed up. Basically all the kana characters that come with voicing markers like が-ga (instead of か-ka) etc. I did not have the time to pursue that issue though.
Then, last night, I found that a colleague of mine had tried to use $@ to feed to a local dictionary application called ding (http://ftp.tu-chemnitz.de/pub/Local/urz/ding/). His problem was with characters that had umlauts. After verifying how he wrote his action I remembered that I had similar issues with Japanese.
Basically his command was "/path/to/ding $@"
That's supposed to use the selected string as an argument to pass to ding, which will launch a Wish application where the string is used as the searched item.
From Terminal, that works a treat. But the exact same line in Automator (with input as argument, not as stdin) messed the composition and the resulting string was not recognized by ding as a match to what it was supposed to match.
So, I tried a few things to get to the core of the issue and found that a simple "echo [accented characters]" was enough to reproduce the difference in string handling between Automator and Terminal. That difference is also reproduced on a number of person's machines.
I have a number of services that basically revolve on "run shell script" actions and involve 3rd party application outputs, preference files etc. so it would not be convenient to show that to you.
I have sent a mail about this issue to the automator list yesterday too:
http://lists.apple.com/archives/Automator-users/2011/Jun/msg00004.html

Trouble using Run Shell Script with python in Automator

Hi. I have a python script I want to run in Automator (update_puzzles.py). All it does is check, rearrange and update files and there is not supposed to be any input. I can get the script to run outside of Automator, in Terminal, by navigating to the right directory and typing "python update_puzzles.py"
I must not be setting up Run Shell Script correctly. I have it set to /bin/bash and Pass Input to stdin. The command line simply reads python /pathname/update_puzzles.py (where pathname is the path to the .py file, which I got by dragging the file onto the Run Shell Script command window). There are no actions before this in my workflow and the action after is View Results.
The log says Run Shell Script failed, and the error is "Traceback (most recent call last):"
Any suggestions?
Thanks so much.

If the script is expecting to do stuff with files in the same directory as the executable, you will probably need to add a statement to change to the appropriate working directory. The shell used in the Automator *Run Shell Script* action is a generic one that does not share any of the environment variables that the Terminal uses.

How to pass video file name to run shell script

Trying to make an automator script that will 1. Start a video capture, 2. Stop video capture, 3. Rename video, 4. Run Shell Script. Here is the shell script:
for f in "$@"
do
echo "$f"
/usr/bin/podcast --server my.podcast.server --user myself --pass mypass --submit --file $f --workflow "my workflow" --metadata /path/to/file
done
Question:
Do I need to create a variable in the automator script to pass it to the script? If I need the variable do I also need to use both Set Value of Variable and Get Value of Variable? If I don't need a variable does $f need quotes around them?

I'm not familiar with the terminal command /usr/bin/podcast so I don't know what it does but what i said is correct. to pass a file to this action you don't need any variables. the previous action in the workflow should output the video file you want to process, that's all. how you arrange that is up to you. it's clear that you have to fill in appropriate things in that shell script like " my workflow" and path to metadata. But if you have questions about how this shell action works you should ask people who made it.

Automator runs shell script differently

hi
i build a little shell script that mounts my network-shares when they are available - that's works perfect if run by terminal but if i run it via Automator-Run shell script it does ******** - it doesn't seem to recognize my variables and creates dirs like $“Data“ instead of just Data
can anyone help me with that?
#!/bin/bash
# connects to network shares if server available
#config - wich server and mountpoints, login
server=$"192.168.2.1"
serverName=$"NAS(AFP)"
dir=$“Data“
dir2=$“Data1“
login=$“xxx“
pw=$“xxx“
#connect-test and create mountfolders
ping -q -c3 $server > /dev/null
if [ $? -eq 0 ];then
if [ -d "/Volumes/"$dir"" ]; then
echo "folder $dir exists"
else
echo "creating folder $dir"
mkdir "/Volumes/"$dir""
fi
if [ -d "/Volumes/"$dir2"" ]; then
echo "folder $dir2 exists"
else
echo "creating folder $dir2"
mkdir "/Volumes/"$dir2""
fi
#mount
mount_afp "afp://"$login":"$pw"@"$serverName"._afpovertcp._tcp.local/"$dir"" "/Volumes/"$dir""
mount_afp "afp://"$login":"$pw"@"$serverName"._afpovertcp._tcp.local/"$dir2"" "/Volumes/"$dir2""
echo „ping ok“
else
echo „failed to connect to $serverName“
fi

FYI. If you create an Alias of a mounted volume, the Alias will record all the connection information, except the password. If your keychain is not locked, then when double clicking on the Alias, it will get the password from the keychain and mount the networked volumes (assumes you allowed the password to be stored in the keychain when you first mounted the volumes interactively).
The Aliases can be put into your System Preferences -> Users & Groups -> Startup Items if you like.
If this is a laptop and you are re-mounting the volumes when you get to a specific location, you might want to look at ControlPlane
<http://www.macupdate.com/app/mac/39644/controlplane>

Run shell script as sudo user without giving sudo passowrd from normal usr

Hi ,
i am running shell script from my account with sudo user what is the problem in my procedure.
Please if any thing wrong in my procedureprocedure or any permission required please let me know.
here is the my procedure and sudo permissions.
[techm@ppsol04 ~]$ sudo su - dadm sudo -u dadm /u01/ora/tools/Dbmon/scripts/export.sh
Sorry, user techm is not allowed to execute '/u01/ora/tools/Dbmon/scripts/export.sh' as dadm on ppsol04.
[dchandu@ppsol04 ~]$ sudo -l
Matching Defaults entries for techm on this host:
env_keep=SSH_AUTH_SOCK, !authenticate, env_reset, always_set_home, !requiretty
sudo permissions :
sudo -l
Matching Defaults entries for techm on this host:
env_keep=SSH_AUTH_SOCK, !authenticate, env_reset, always_set_home, !requiretty
User techm may run the following commands on this host:
(ALL) NOPASSWD: /local/bin/hardened_profile.sh
(root) NOPASSWD: /bin/su - dora
(root) NOPASSWD: /bin/su - doraadm
(root) NOPASSWD: /bin/su - docenter
(root) NOPASSWD: /bin/su - tora
(root) NOPASSWD: /bin/su - toraadm
(root) NOPASSWD: /bin/su - tocenter
(root) NOPASSWD: /bin/su - hora
(root) NOPASSWD: /bin/su - horaadm
(root) NOPASSWD: /bin/su - hocenter
(root) NOPASSWD: /bin/su - agcfdwf4
(root) NOPASSWD: /bin/su - pora
(root) NOPASSWD: /bin/su - dadm
(root) NOPASSWD: /bin/su - pocenter
(root) NOPASSWD: /bin/su - agcfdwp4
Thanks
tech

Can you please explain what you are trying to accomplish?
To my understanding there is no such thing like a sudo password for a normal user. Sudo allows users to become root based on a sudo list (suoders). The user is then prompted for their own account password to run as super-user or root.

Run Shell Script: Interaction?

I use a shell script to build and edit blog articles.
It's quite clever when on the local server where the files end up. A simple routine of building a .php file, then it launches Vim on the file it created, I make some edits to it (add the content), then save and exit Vim.
That is it. When done on the local server, this is perfect. However, with my new upgrade to Tiger, I wanted to try using Automator to do some of this as well as the image copy and conversions which I typically do beforehand.
The Workflow I have so far actually works but the SCRIPT part is messing with me.
I need to have Automator launch the script in a Terminal window so I can interact with the steps it goes thru. Essentially, the launch of Vim in the Terminal opening the file that was made.
I can't figure out how to do this. Terminal is not an app in the left pane of Automator, and when I call my script using "Run Shell Script", it does not perform the last step, "vi filename.php" - rather it completes and leaves my "Stencil" un-edited.
How can I get this done?
Beavis2084

http://discussions.apple.com/message.jspa?messageID=1791477#1791477

Apple Automator - Run Shell Script Application

Morning, hope somebody can point of my error please.
I'm attempting to create an Application wrapper for a minecraft server.
I've done the following
Automator > Application
I've dragged in 'Run Shell Script'
The Shell dropdown is '/bin/bash'
The Pass input is 'as arguments'
In the script I have '
cd /Volumes/3Tb/Bukkit_live
/usr/bin/java -Xmx2G -jar /Volumes/3Tb/Bukkit_live/minecraft_server.jar nogui
Now when I run it through the automator app, it works fine, the server starts, however when I try and run it as a standalone application it does nothing ?
Please help.
Thanks in advance.
Darren

Best guess is that there is an environment variable in your Terminal session that does not exist when you are running an Automator workflow.
You could try running an Automator workflow that does Run Shell Script with something like
( pwd
id -a
echo $#
echo "$@"
printenv
) >/tmp/automator.environment.txt
Then do 2 things. Run it within Automator and copy the /tmp/automator.environment.txt file someplace safe. Next save it as an Automator app and run it that way. Compare the 2 automator.environment.txt files and see if anything significant is different between the 2.
This is just a guess (an educated guess, as this sort of thing has happened to others in the past when they see a difference between running a script interactively and running it as an embedded app).

Cannot add "Run shell script" to workflow

Just like the subject says on an iBook G4, OS X 10.4.8. The previous solution of deleting the Automator cache file in ~/Library did not work for me. The console log does show an error when I attempt to drag Run Shell Script to the workflow error:
2006-11-25 21:15:32.909 Automator[545] * -[NSTextView replaceCharactersInRange:withString:]: nil NSString given.
I do have an updated bash installed using DarwinPorts, however that is installed to /opt/local/bin, which appears in my path before /usr/bin. This isn't causing problems on my cube, though.
Any ideas?

You might have a corrupted file in the action, in which case you could reload it with something like Pacifist. You can't get the digest of a directory, so for comparison, compressing a copy of /System/Library/Automator/Run Shell Script.action on my desktop gives me the following:
sha1 digest: c209b69777f6a3301d72ddf0eb0ad4e7d4230741
md5 digest: 09e4ade9056ada3294ffb93bd16de1a7

Running shell scripts from within oracle. A big task is forgotten

Dear List,
I have some shell shell scripts which do some tasks on the linux OS level.
I am calling the Korn scripts using a java class, which in turn is being called from a PLSQL function.
All but one of the 10 script works fine. This is the script which does the most work, and takes on average 40 minutes usually.
Why does Oracle forget the running of the shell script? I wait in my PLSQL function for the return code, but it never comes. The scripts I have not written myself !
I look forward to your reply on this matter.
regards
Ben

Hi
If you are using the Oracle database 10g, the new dbms_scheduler package allows you to run shell scripts. The dbms_scheduler.create_job procedure have one parameter called the job_action in which you specify the full path of the shell script.
I hope this will help

How to run shell script using External Process in Process Flow?

Hi,
We can run external process using Process flow.
I would like to run shell script as external process in Process flow.
Could any one please explain it?
Thanks and regards
Gowtham Sen.

HI,
As you said I tried this case. I got the following error. The script is running successfully while I tested at unix command prompt.
The error is as follows..
tarting Execution PFPS_SMPL_RUNSHELL
Starting Task PFPS_SMPL_RUNSHELL
Starting Task PFPS_SMPL_RUNSHELL:EXTERNALPROCESS
/SOURCE_FILES/CollectFiles.sh: line 1: ls: command not found
/SOURCE_FILES/CollectFiles.sh: line 1: wc: command not found
/SOURCE_FILES/CollectFiles.sh: line 1: ls: command not found
Completing Task PFPS_SMPL_RUNSHELL:EXTERNALPROCESS
Starting Task PFPS_SMPL_RUNSHELL:EXTERNALPROCESS_1
SQL*Plus: Release 10.1.0.2.0 - Production on Fri Sep 29 22:57:39 2006
Copyright (c) 1982, 2004, Oracle. All rights reserved.
ERROR:
ORA-12545: Connect failed because target host or object does not exist
Enter user-name: SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
where <logon> ::= <username>[<password>][@<connect_identifier>] | /
Enter user-name: SP2-0306: Invalid option.
Usage: CONN[ECT] [logon] [AS {SYSDBA|SYSOPER}]
where <logon> ::= <username>[<password>][@<connect_identifier>] | /
SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
Completing Task PFPS_SMPL_RUNSHELL:EXTERNALPROCESS_1
Completing Task PFPS_SMPL_RUNSHELL
Completing Execution PFPS_SMPL_RUNSHELL
My scenario is---
I am trying to return a file name from one shell script. I created a external process for that. After completion of this process, I am running another script which takes that file name and trying to create a external table. The both scripts are runnning successfully. But while I am trying to run using process flow, its not coming.
And I am not getting the way to catch the output of external process and pass it as parameter as another external process.
Any suggestions are welcome.
Thanks and regards
Gowtham Sen.

Problems to run shell scripts in terminal

Similar Messages

Maybe you are looking for