Any fix for cron jobs yet with chrootsh?

[HostaHost]

Is there any hope of seeing a fix for the broken crontab issue in Plesk 10? Right now, if a user is set to chrootsh, they cannot run cron jobs because their crontab is set to have the useless SHELL=/usr/local/psa/bin/chrootsh.

The docs at http://download1.parallels.com/Plesk/PP10/10.2.0/Doc/en-US/pdf/plesk-10-administrator-guide.pdf on page 166 describe a way to set a shell just for cron:

/usr/local/psa/admin/bin/server_pref -u -crontab-secure-shell ―/bin/sh‖

That path is wrong and should be /usr/local/psa/bin/server_pref, but even once corrected, the setting has no effect on the crontab if the user is set to chrootsh. It only changes the crontab if the user is set to Forbidden for the shell. I need to let users run jobs and give them chrootsh for access; any way to get around that yet?

 

[HostaHost]

Several months, still broken...

 

[Mickael Salfati]

Re

Bump on this topic. I saw a lot of topics about this issue and I confirm it.

Debian 6 Plesk 10.4.4 MU32 x64, no way to launch crontab (like wget curl) even if I enable /bin/sh in domain's configuration.

Thanks per advance.

 

[sophieG]

You can find all Job Decriptions on our blog

 

[abdi]

Is there any hope of seeing a fix for the broken crontab issue in Plesk 10? Right now, if a user is set to chrootsh, they cannot run cron jobs because their crontab is set to have the useless SHELL=/usr/local/psa/bin/chrootsh.

The docs at http://download1.parallels.com/Plesk/PP10/10.2.0/Doc/en-US/pdf/plesk-10-administrator-guide.pdf on page 166 describe a way to set a shell just for cron:

/usr/local/psa/admin/bin/server_pref -u -crontab-secure-shell ―/bin/sh‖

That path is wrong and should be /usr/local/psa/bin/server_pref, but even once corrected, the setting has no effect on the crontab if the user is set to chrootsh. It only changes the crontab if the user is set to Forbidden for the shell. I need to let users run jobs and give them chrootsh for access; any way to get around that yet?

You know you can adjust the permissions for each of the SHELL to enable users access certain folders / procs on the server. There is an article for that in the KB.