12-29-2008
How to resolve bad interpreter error
Hi,
Using yum I had installed csh in /usr/bin
When I give which csh it gives
/bin/csh
Output of the commands given by you:
[root@137 utils]# head -n 1 AllCodeManagerFix
#!/usr/bin/csh
[root@137 utils]# head -n 1 AllCodeManagerFix |od -cx
0000000 # ! / u s r / b i n / c s h \n \0
2123 752f 7273 622f 6e69 632f 6873 000a
0000017
After instaling csh I also tried giving csh ./AllCodeManager and now it throws error
WARNING : no CodeManagerFix in SCCS
Does this show that the command has run or is it a error.
After this command when i give gmake Linux:
root@137 SCCS]# gmake LINUX
gmake: *** No rule to make target `LINUX'. Stop.
Please let me know what needs to be done.
Regards,
vijaya.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
today i started the LFS book (version 4.0).
Basically i am using slackware 9.0 to try and install a new linux completely from source on another partition.
Now i took the book's recommendations and created a user called lfs so i wouldn't have to do the stuff as root, and i have got the new LFS... (4 Replies)
Discussion started by: Calum
4 Replies
2. UNIX for Dummies Questions & Answers
I am writing an expect script but am getting a bad interpreter: permission denied error.
I don't think the error has anything to do with expect itself, I think I am missing something in how I start the file. For instance, when I run the file under the expect directory it works:
cd... (7 Replies)
Discussion started by: earnstaf
7 Replies
3. Shell Programming and Scripting
Here is a puzzler.
To start, let me say that I've done a search on this issue and it is definitely not related to line endings being encoded in windows returns.
I get this error when I run SOME perl scripts. I have a script called hello_world.pl. I do $cp hello_world.pl new_hello_world.pl... (0 Replies)
Discussion started by: mjmtaiwan
0 Replies
4. Shell Programming and Scripting
Hi Gurus,
I am new to scripting and needs your help in expect script used for telnet. I wrote a simple script as
#!/usr/bin/expect-5.43 -f
spawn telnet localhost 2233
expect "password:"
send "secret\r"
send "i data.cnbc.com\r"
send "exit\r"
expect eof
When I am trying to execute... (2 Replies)
Discussion started by: niks_yv
2 Replies
5. Shell Programming and Scripting
Hi
I am running a script:
#!bin/bash
set -x
echo"select * from celldatamap;" || sqlcsv -v -h -s ',' -d MTNSA11G -u datasafe -p datasafe > andrea.csv
When I run my script
./tablescript.sh
I get the following error:
$ ./tablescript.sh (3 Replies)
Discussion started by: ladyAnne
3 Replies
6. Shell Programming and Scripting
Hi All,
I'm not confortable in writing script, can someone can help me, when I run that script below i found this error code : -bash: ./script.sh: /bin/sh.: bad interpreter:
Here is the script
for i in *
x=${i##*.}
z=$(perl -e 'print time;')
t=$(echo $z-$x|bc)... (12 Replies)
Discussion started by: bzb23
12 Replies
7. Shell Programming and Scripting
Hi. My name is Caleb (a.k.a RagingNinja) form the whited00r forums. (Whited00r makes custom firmware for iOS devices).
I have been learning and creating simple shells scripts. I have been recently using VIM for Windows or using VirtualBox to run the UBUNTU OS within VirtualBox to create my shell... (2 Replies)
Discussion started by: RagingNinja
2 Replies
8. Red Hat
Hi,
I accidentally did this:
wadhwaso@nxsdgd01 deps]$sudo rpm -e --nodeps glibc-2.5-107.x86_64
error: %postun(glibc-2.5-107.x86_64) scriptlet failed, exit status 255
and since then I am not able to run any command on this server except 'cd'.
I always get the following error:
$ ls... (6 Replies)
Discussion started by: stunn3r
6 Replies
9. UNIX for Advanced & Expert Users
Hi all
I'm hoping this is just me being a muppet, has anyone come across this problem before?
I am writing an application that uses sqlite3 and I have created a database using it -
sqlite3 muse.db
SQLite version 3.6.20
Enter ".help" for instructions
Enter SQL statements terminated with... (2 Replies)
Discussion started by: steadyonabix
2 Replies
10. Shell Programming and Scripting
I keep getting this error and I am not sure why.
-bash: ./p4: /bin/ksh^M: bad interpreter: No such file or directory
First I run my makefile and this works fine:
goodmain: main.o
gcc -o goodmain main.o
main.o: main.c
gcc -c main.c
Then I want to limit my output so I... (11 Replies)
Discussion started by: cokedude
11 Replies
LEARN ABOUT OPENSOLARIS
echo
echo(1B) SunOS/BSD Compatibility Package Commands echo(1B)
NAME
echo - echo arguments to standard output
SYNOPSIS
/usr/ucb/echo [-n] [argument]
DESCRIPTION
echo writes its arguments, separated by BLANKs and terminated by a NEWLINE, to the standard output.
echo is useful for producing diagnostics in command files and for sending known data into a pipe, and for displaying the contents of envi-
ronment variables.
For example, you can use echo to determine how many subdirectories below the root directory (/) is your current directory, as follows:
o echo your current-working-directory's full pathname
o pipe the output through tr to translate the path's embedded slash-characters into space-characters
o pipe that output through wc -w for a count of the names in your path.
example% /usr/bin/echo "echo $PWD | tr '/' ' ' | wc -w"
See tr(1) and wc(1) for their functionality.
The shells csh(1), ksh(1), and sh(1), each have an echo built-in command, which, by default, will have precedence, and will be invoked if
the user calls echo without a full pathname. /usr/ucb/echo and csh's echo() have an -n option, but do not understand back-slashed escape
characters. sh's echo(), ksh's echo(), and /usr/bin/echo, on the other hand, understand the black-slashed escape characters, and ksh's
echo() also understands a as the audible bell character; however, these commands do not have an -n option.
OPTIONS
-n Do not add the NEWLINE to the output.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscpu |
+-----------------------------+-----------------------------+
SEE ALSO
csh(1), echo(1), ksh(1), sh(1), tr(1), wc(1), attributes(5)
NOTES
The -n option is a transition aid for BSD applications, and may not be supported in future releases.
SunOS 5.11 3 Aug 1994 echo(1B)