• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Cronjob + Chroot Problem

futureweb

Regular Pleskian
Hello,

following Problem: Cronjob was created with BASH (CHROOT) Setting on User.
Later the CHROOT Setting got deleted (User got fully BASH Access) - but within the CRON the CHROOT definition was not deleted ... (Environment variable SHELL = /usr/local/psa/bin/chrootsh)

Only affecting my installation or a general Bug?

Andreas Schnederle-Wagner
 
Hello,

following Problem: Cronjob was created with BASH (CHROOT) Setting on User.
Later the CHROOT Setting got deleted (User got fully BASH Access) - but within the CRON the CHROOT definition was not deleted ... (Environment variable SHELL = /usr/local/psa/bin/chrootsh)

Only affecting my installation or a general Bug?

Andreas Schnederle-Wagner

sysuser has (or has no) access to server independently with cron tasks.
The users cron tasks always created under chrootsh environment for security reasons. At the same time, user may have(or have no) ssh access to server because it's independent and different permissions.
You may set all these permissions on subscription customization screen or in service plan properties:
- Management of access to the server over SSH
- Scheduler management
 
Back
Top