cron jobs and chroot shell are broken on 10.2

[HostaHost]

So unless we give a customer a full /bin/bash shell, they can't log in at all using ssh and also can't set up cron jobs. In 10.2, if you try to ssh in when you have chroot shell set, you get this:

Last login: Wed Jun 29 12:32:54 2011 from localhost.localdomain
execv("/bin/bash") failed
system error: No such file or directory


And, in 10.2, customers' cron jobs are created with this in the crontab file:

SHELL=/usr/local/psa/bin/chrootsh

which causes any 'scheduled task' they create to fail with the same 'execv("/bin/bash") failed' error.

 

[breun]

The Administrator's Guide shows how to change the shell for cronjobs: http://download1.parallels.net/Ples...US/online/plesk-administrator-guide/66791.htm

 

[HostaHost]

The Administrator's Guide shows how to change the shell for cronjobs: http://download1.parallels.net/Ples...US/online/plesk-administrator-guide/66791.htm

The administrator guides that Parallels produces often show things as being possible when they aren't. I take it you haven't actually tried what the guide says since the command is not even in the right location for starters. If you do find the correct location and use it, the setting has absolutely no effect if the user is set to the chrootsh shell. The user needs to either have a Forbidden shell, or a full shell, and if they've been given a full shell, then you would not encounter the problem in the first place. So the problem comes back to being one of you can either deny customers SSH access, or deny them cron job access, since they can't have both unless you give them unrestricted access to the server.

 

[breun]

I reported the path error to the docs team. I hope the functionality gets fixed also.