Forum Moderators: phranque

Message Too Old, No Replies

Accessing Apache cron jobs front end interface

cron jobs

         

matc

4:08 pm on Mar 8, 2004 (gmt 0)

10+ Year Member



Hello all,

I want to build a front end interface that displays all cron jobs based on our production server Linux 9, Apache 1.3x.
Basically, I would like to allow all the cron jobs to be listed with options to turn them off/on, re-run them and change their fequency. I have seen this crontab interface but it is too over the top for what I had planned: [webmin.com....] plus I would like to build my own.

Simply question really where do I start with this?
Any help with this would be much appricated.

cheers, ject

hyperbole

6:41 pm on Mar 8, 2004 (gmt 0)

10+ Year Member



I'd like to warn you that what you are trying to do is dangerous and will allow others to access your server in ways you may not want.

If you are trying to make an interface that would only ba accessable to you via your own internal net and you can controll access to the interface, this is much safe. I would not recommend making such an interface generally available on the net.

Try looking at the documentation for cron. You will find reference to a file called 'crontab' (I think it is usually in /etc/) There is also a man page (i think in section 8) on crontab. You will need root access to access this table directly.

You can look at the contents of crontab by entering the command 'cron -e'. Be careful, any changes you make will update the crontab.

Again let me warn you that you really need to know what you are doing to fool around with the crontab.

Let me know if this points you in the right direction, and if there is anything else I can tell you to help.

lemat

1:16 am on Mar 9, 2004 (gmt 0)

10+ Year Member



you can use server-side scripts (PHP,Perl...) to manage a file, and you can set a cron job, to look into this file and do what this file contains. for egzample this file may say: "install new crontab job: * * * * * /job" or
"run this immediately: /job"

Remember - you were warned in previous post.

matc

11:12 am on Mar 11, 2004 (gmt 0)

10+ Year Member



Hi and thanks for the pointers.

Luckily the system won't be accessed or made available to anyone outside our own local development network.

I'm hoping the panel will allow non-techical members to restart/edit cronjobs if no-one else is around to help. I think its a good move to have it as command lines is pretty alien for most of them. However, I still have to run it past our system administrator and get all our present crons trimmed and in one shared directory.

Thanks again :)