bash: ./myscript: /usr/bin/env: bad interpreter: Text file busy"myscript" begins with #!/usr/bin/env python. Just retrying starting it fixed the problem.
Why system program env sporadically becomes "busy"? Can it be caused by prelink (but cron should start it not at that time...)
2 Answers
Commenters say that it is script busy, not env or python and is caused by text editor saving it.
Usualy it's "./myscript" witch is busy because another program modify the file. It can be a text editor (when save it) but also a remote copy (This can be long if the download rate is low) or another program.
