teleute

Member
Apr 18, 2005
11
0
151
I swear I've read something in the past, but I can't find it now - does it mess up cPanel's handling of cron jobs if you manually edit the crontab? I have crons working on all my sites except one - when I add the commands in cpanel, they just get wiped out. I'm starting to suspect that someone before me may have edited the crontab. Any other possibilities? And if that is the case, how do I fix it? Thanks!
 

brianoz

Well-Known Member
Mar 13, 2004
1,146
7
168
Melbourne, Australia
cPanel Access Level
Root Administrator
I think manual edits are OK; but you'd have to restart cron after the edit so it noticed the change.

Are you doing the changes with the crontab(1) command?

("OK" above does not mean recommended! I'd use crontab -l and crontab in a loop instead for global edits!)
 

teleute

Member
Apr 18, 2005
11
0
151
I think manual edits are OK; but you'd have to restart cron after the edit so it noticed the change.

Are you doing the changes with the crontab(1) command?

("OK" above does not mean recommended! I'd use crontab -l and crontab in a loop instead for global edits!)
I just want to do the edits in cPanel and have them work. I'm not interested in manually editing - I just think maybe it was done in the past and that's what's causing the issue, but perhaps that's not the case. All I know is, cron works on all accounts but one, and when I try to add jobs in cpanel for the one, they just disappear/don't work.
 

Website Rob

Well-Known Member
Mar 23, 2002
1,501
1
318
Alberta, Canada
cPanel Access Level
Root Administrator
The "crontab" is specifically for the Server, not any User accounts and should only be editted using:
crontab -e


As to the one account having cron problems, run this command: cat /etc/cron.deny
If you see the Username of the problem account then that's the problem. Simply edit the file and remove the Username. No restart of cron required.
 

teleute

Member
Apr 18, 2005
11
0
151
The "crontab" is specifically for the Server, not any User accounts and should only be editted using:
crontab -e


As to the one account having cron problems, run this command: cat /etc/cron.deny
If you see the Username of the problem account then that's the problem. Simply edit the file and remove the Username. No restart of cron required.
Thanks...I looked in cron.deny and there's only "nobody". Any other reasons one user only might be having issues?