>> On 1/8/16, David Henderson <[email protected]> wrote: >>> I haven't seen any evidence of this, but do I need to create an >>> /etc/crontab config file? I'm looking at my Debian system and it >>> doesn't have anything in theres to process the cron.d directory >>> contents, only cron.hourly, cron.monthly, etc... >>> >>> Dave >>> >>> >>> On 1/8/16, David Henderson <[email protected]> wrote: >>>> Good morning, are there any BB developers that monitor this list to >>>> offer help? Is there another place that I can get this issue >>>> resolved? >>>> >>>> I have made sure that the ownership of the cron.d folder are both root >>>> and carries 775 permissions. I've also made sure the files contained >>>> within are also owned by root and also have a 775 permission set. >>>> >>>> Thanks, >>>> Dave >>>> >>>> >>>> On 1/7/16, David Henderson <[email protected]> wrote: >>>>> Greetings, since I already have the cron daemon running (verified via >>>>> ps), I tried setting up an example by creating the /etc/cron.d >>>>> directory and creating a test file: >>>>> >>>>> * * * * * echo 'hello world' >> /tmp/test.txt >>>>> >>>>> This does not appear to be picked up by cron. So looking at the help >>>>> output, I thought I should be using the '-c' parameter: >>>>> >>>>> crond -c /etc/cron.d >>>>> >>>>> Once again, this appears to fail. Any thoughts on why this isn't >>>>> working? >>>>> >>>>> Thanks, >>>>> Dave >>>>> >>>> > > Hi, > > //config: help > //config: Crond is a background daemon that parses individual crontab > //config: files and executes commands on behalf of the users in > question. > //config: This is a port of dcron from slackware. It uses files of the > //config: format /var/spool/cron/crontabs/<username> files, for example: > //config: $ cat /var/spool/cron/crontabs/root > //config: # Run daily cron jobs at 4:40 every day: > //config: 40 4 * * * /etc/cron/daily > /dev/null 2>&1 > > Ciao, > Tito
Thanks for the reply Tito! So does the -c parameter change the parsing directory from /var/spool/cron/crontabs, or does it specify a 'holding' directory for the individual cron jobs? Also, does that mean that I can't implement something like an /etc/cron.d directory where any cron jobs within it are parsed, or can I create an /etc/crontab file to parse that directory using run-parts? Thanks, Dave _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
