Submitted by diegoweb on Mon, 06/22/2020 - 11:15 Pro Licensee
The option is enabled in System Settings > Server Templates > Default Settings > Administrato's Webmin Modules > Scheduled Cron Jobs (user's process only) but the user can't see the menu to set up the cron jobs.
Is this a bug? How do I grant all virtualmin server owners to access their own cron jobs?
Thanks!
Status:
Closed (works as designed)
Comments
Submitted by diegoweb on Mon, 06/22/2020 - 11:16 Pro Licensee Comment #1
Submitted by JamieCameron on Mon, 06/22/2020 - 17:16 Comment #2
You should be able to access them at Webmin -> System -> Scheduled Cron Jobs.
Submitted by diegoweb on Thu, 06/25/2020 - 21:40 Pro Licensee Comment #3
Jamie, as a ROOT user I can see them where you've mentioned. But as a Virtualmin Server Owner, this options doesn't exist. Please, check the printscreens I've attached in the topic.
The second screenshot (chrome_22-06-2020_13-15-59.png) although in Portuguese, only shows: Sistema (System): Alterar Senha (Change Password) Histórico do Sistema (System Log).
It's missing the Scheduled Cron Jobs option.
Submitted by JamieCameron on Fri, 06/26/2020 - 18:43 Comment #4
Are the domains for which this is happening on the Default virtualmin template?
Submitted by diegoweb on Fri, 06/26/2020 - 18:54 Pro Licensee Comment #5
Yes. There's only one Virtualmin Template available and in use, which is the default one.
Submitted by JamieCameron on Sat, 06/27/2020 - 14:08 Comment #6
Can you post the line from the /etc/webmin/webmin.acl file that starts with the domain owner's username?
Submitted by diegoweb on Sat, 06/27/2020 - 20:09 Pro Licensee Comment #7
username: mysql virtual-server filemin passwd updown change-user htaccess-htpasswd syslog phpini virtualmin-awstats virtualmin-htpasswd
All virtual server owner share the same setup above.
Submitted by JamieCameron on Sat, 06/27/2020 - 20:11 Comment #8
I just realized one reason why this may happen - does this domain have a chroot jail enabled?
Submitted by diegoweb on Sat, 06/27/2020 - 20:32 Pro Licensee Comment #9
Yes! All domains have chroot jail.
Submitted by JamieCameron on Sat, 06/27/2020 - 20:57 Comment #10
Ok, this is expected then. The reason is that Cron has no way to chroot commands, so if we did allow domain owners to create their own Cron jobs, they could escape from the jail.
Submitted by diegoweb on Sat, 06/27/2020 - 22:40 Pro Licensee Comment #11
What's the best approach to create cron jobs for users, then? Myself as root create the cron for the user, and use their username to run the command? Or since chroot jail is enabled, I can't let them have cron jobs, no matter the way?
Submitted by JamieCameron on Sun, 06/28/2020 - 01:48 Comment #12
Currently, you would have to create cron jobs, which run under their username.
Submitted by diegoweb on Sun, 06/28/2020 - 09:28 Pro Licensee Comment #13
OK! Thanks Jamie!