• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Simple Cron Script.... (bad interpreter)?

J

jvanv8

Guest
I tried to run a simple cron from a custom script by entering the script in the "Command" section under the "Crontab Tasks"
My script was as follows:
Code:
ls
As you can see, I just wanted to see if it worked. I got an email with the error message:
Code:
line 1: 
ls
: command not found
So I saw that some people start their scripts with some stuff at the beginning called "shebang"(?) I think. Anyway, I changed my script to this:
Code:
#!/bin/sh
ls
When this was run, I get the email:
Code:
/bin/sh: /home/httpd/vhosts/mydomain.com/httpdocs/cronjobs/my_cron: /bin/sh
ls

: bad interpreter: No such file or directory
What the heck? How can I fix this script so it works with Plesk?
 
Back
Top