1

I tried crontab -e and the file that was edited is /tmp/crontab.vJdE7J/crontab. Is this correct?

I read from http://www.devils-heaven.com/raspberry-pi-cron-jobs/ that I should be creating a schedule file in /etc/cron.d instead.

I tried the first method, and couldn't verify that any scheduled task was run. I tried the second method and it worked for me. When I added a second file in /etc/cron.d, it was not run. Is there a need to reinitialize the cron process? Or does /etc/cron.d allow only one cron file?

closed as off-topic by lenik, Bex, RPiAwesomeness, Steve Robillard Dec 2 '14 at 1:56

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "This question does not appear to be specific to the Raspberry Pi within the scope defined in the help center." – lenik, Bex, RPiAwesomeness, Steve Robillard
If this question can be reworded to fit the rules in the help center, please edit the question.

  • This would probably fit better on Unix & Linux as that is a Linux-centric Stack Exchange site and this is a generic Linux question, not Raspberry Pi-specific. However, if you've used these exact commands on another Linux system and haven't had issues there, then this question would be on-topic here. – RPiAwesomeness Nov 20 '14 at 12:37
4

When you use crontab -e, make changes, and then save, it saves the new crontab into a temporary file, presumably does a little verification, then automatically copies the temporary file to the proper location.

You seem to be describing normal crontab -e behaviour.

Use crontab -l to see if your changes were properly committed.

Not the answer you're looking for? Browse other questions tagged or ask your own question.