Login or Register to Ask a Question and Join Our Community


UNIX for Dummies Questions & Answers

bad interpreter: Permission denied

 
Thread Tools Search this Thread
Top Forums UNIX for Dummies Questions & Answers bad interpreter: Permission denied
# 8  
Old 07-19-2007
Quote:
Originally Posted by porter
you should be able to do


Code:
cd
/usr/bin/expect

and this should run the interpreter.
I can run the script with #!/usr/local/bin/expect which is a bit confusing to me since I thought it only existed within /usr/bin/expect/expect...

Thanks for your help porter... being able to call it has /usr/local/bin/expect will work fine.

Thanks agian.
 
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

-bash: ./p4: /bin/ksh^M: bad interpreter: No such file or directory

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

2. UNIX for Advanced & Expert Users

Sqlite3: /lib/ld-Linux.so.2: bad ELF interpreter:

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

3. Red Hat

Not able to run any command /lib64/ld-Linux-x86-64.so.2: bad ELF interpreter

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

4. Shell Programming and Scripting

Bad Interpreter

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

5. Shell Programming and Scripting

bad interpreter when running script

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

6. Shell Programming and Scripting

bad interpreter: Permission denied

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

7. Shell Programming and Scripting

Executing expect script giving message as bad interpreter: Permission denied

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

8. Shell Programming and Scripting

Perl - bad interpreter: No such file or directory

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

9. Ubuntu

How to resolve bad interpreter error

Hi, Iam trying to run a gmake command and have the latest version of Gnu in my redhat linux system. I need to execute the following steps; ---> chmod +x utils/* ---> ./utils/AllCodeManagerFix ---> gmake LINUX Iam able to do the chmod command but when I run the second command I get... (2 Replies)
Discussion started by: viji19812001
2 Replies

10. Shell Programming and Scripting

/bin/sh: bad interpreter: Permission denied

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
Login or Register to Ask a Question

LEARN ABOUT OSF1

badsect

badsect(8)						      System Manager's Manual							badsect(8)

NAME

       badsect - Creates files to contain bad sectors

SYNOPSIS

       /usr/sbin/badsect bbdir sector...

DESCRIPTION

       The  badsect  command  makes  a file to contain a bad sector.  Normally, bad sectors are made inaccessible by the standard formatter, which
       provides a forwarding table for bad sectors to the driver. If a driver supports the bad blocking standard, it is  preferable  to  use  that
       method  to isolate bad blocks because the bad block forwarding makes the disk appear perfect, and such disks can then be copied with dd(1).
       The technique used by badsect is also less general than bad block forwarding, as badsect cannot make amends for bad blocks in the i-list of
       file systems or in swap areas.

       On  some  disks,  adding  a  sector  that is suddenly bad to the bad sector table currently requires the running of the standard formatter.
       Thus, to deal with a newly bad block or on disks where the drivers do not support the bad-blocking standard, badsect can be  used  to  good
       effect.

       Use the badsect command on a quiet file system in the following way: Mount the file system and change to its root directory.  Make a direc-
       tory BAD there.	Run badsect, giving as argument the BAD directory followed by all the bad sectors you wish to add.   (The  sector  numbers
       must  be  relative to the beginning of the file system, as reported in console error messages.)	Change back to the root directory, unmount
       the file system, and run fsck(8) on the file system.  The bad sectors should show up in two files or in the bad sector files and  the  free
       list.   Have  fsck  remove  files containing the offending bad sectors, but do not have it remove the BAD/nnnnn files.  This operation will
       leave the bad sectors in only the BAD files.

       The badsect command works by giving the specified sector numbers in a mknod(2) system call, creating an	illegal  file  whose  first  block
       address	is  the  block containing bad sector and whose name is the bad sector number.  When fsck discovers the file, it will ask "HOLD BAD
       BLOCK?"	An affirmative response will cause fsck to convert the inode to a regular file containing the bad block.

RESTRICTIONS

       If more than one of the sectors comprised by a file system fragment are bad, you should specify only one to badsect, as the blocks  in  the
       bad sector files cover all the sectors in a file system fragment.

ERRORS

       The  badsect  command refuses to attach a block that resides in a critical area or is out of range of the file system.  A warning is issued
       if the block is already in use.

SEE ALSO

       Commands: fsck(8)

																	badsect(8)