cron jobs per user

[arrn]

is there anything planed to add a cron job interface to ispconfig ?
if not i think it would be a perfect idea.

[falko]

Yes, it is planned, but I don't know when it will be available.

[NETabuse]

there really is no need for this,, Maybe i'm wrong, but if a user has been granted shell access for their account, they should be able to perform crontab -e; So conjobs for the user are not a problem.
I believe that the admin user for a domain would have access to any files you need to affect with cron jobs. all users in the webX group would have permissions to change the files (they should be group writable.)

If i'm wrong, let me know.

[arrn]

sure if they have shell, but if not ?!?

[NETabuse]

True, web interface for the users crontab -e interface would be ideal. I was thinking about this earlier in the week, then just said to heck with it, i'll just throw shell access to the users who request scheduled tasks.

[wpwood3]

I would like to see web based cron in ISPConfig, too.

I have this in Plesk now and will miss it when I dump Plesk. Each user has access to a cron for their website and there is a system wide cron for root. It's not a must have but it is nice to have.

[mlz]

I disagree, I believe this is a must have for any host that wants to present a professional image. This issue and the lack of multi-server is probably ISPConfigs biggest downfalls to us, one that will hopefully be rectified sooner than later.

[Compactman]

Throw me on the list for this feature request as well.

[tensor]

Giving ability to make cron jobs effectively gives user a shell, unless the admin approves/disapproves the entries in cron jobs.
And it may involve user editable scripts, so even if the admin approves that, the user may change the script to make a back connecting shell.

[Compactman]

Then put a warning on the feature and give the admin control over the option if they want to enable it for the users account. Just because a security risk can be posed by the user who you have already granted access to an account does not mean the user is going to take advantage of it.

But don't cripple the software just because there may be less informed admins out there.

Originally Posted by tensor

Giving ability to make cron jobs effectively gives user a shell, unless the admin approves/disapproves the entries in cron jobs.
And it may involve user editable scripts, so even if the admin approves that, the user may change the script to make a back connecting shell.