• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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