For ages I've gotten used to editing Perl CGI scripts in "vi" and simultaneously having a browser open to test them. Lately, I've been getting "500" server errors when I do that, and when I run the script from the shell, I get "bad interpreter: Text file busy". The only solution is to exit "vi" whenever I want to test the script, which is a royal pain and should be totally unnecessary. What's up with that? I'm running a Debian server, which I keep updated regularly, and I'm assuming it started with some so-called "upgrade" 🙂
Debian – bad interpreter: Text file busy
500cgidebianperlvi
Related Topic
- Restarting a Perl-script (socket daemon) from /etc/inittab
- CGI script not working properly on new web server
- Unable to SSI include some CGI scripts
- Need help running CGI scripts on Mac OS X Apache
- Apache: Permission denied: exec of ‘/var/www/html/cgi-test/first.pl’ failed
- CGI errors (Can’t open perl script / Permission denied)
Best Answer
You appear to be having this issue, which is because at some point
nvi
started opening filesO_RDWR
instead ofO_RDONLY
.If your
vi
is in factnvi
, I'd try using a differentvi
, sayvim
.