• 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.

Chroot cron shell for users with a non-chroot shell

breun

Golden Pleskian
According to Execution of Scripts via Cron Task Scheduler (Linux Hosting) in the Administrator's Guide all cronjobs are run using a chroot shell. To me it would make sense that users with a non-chroot shell configured should also be able to run commands using this non-chroot shell. Does this make sense to others?

I understand that it's possible to change the cron shell to some non-chrooted shell using the server_pref command as explained in the documentation, but I think it'd be better if there was no need to change this shell server-wide.
 
Back
Top