WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: crond TCL version 11.1  (Read 2766 times)

Offline mocallins

  • Newbie
  • *
  • Posts: 11
crond TCL version 11.1
« on: December 22, 2020, 01:08:07 PM »
I've tried pretty much everything i found with a  google search of cron(d) and @reboot.

Even tried different spellings of @reboot (all lower case, all uppercase, just capital R),
nothing helps.
 the example "* * * * *  sh /home/tc/bin", works as expected and bothers you every minute.

Started with debug level 0, find no errors.

Offline Rich

  • Administrator
  • Hero Member
  • *****
  • Posts: 11694
Re: crond TCL version 11.1
« Reply #1 on: December 22, 2020, 01:25:40 PM »
Hi mocallins
I've tried pretty much everything i found with a  google search of cron(d) and @reboot. ...
There is no command called  @reboot.  There is a  reboot  command and it needs to be run as root:
Code: [Select]
sudo reboot

Offline curaga

  • Administrator
  • Hero Member
  • *****
  • Posts: 11049
Re: crond TCL version 11.1
« Reply #2 on: December 22, 2020, 02:02:59 PM »
I don't think busybox cron supports all those special timings. See busybox docs and the source for details.
The only barriers that can stop you are the ones you create yourself.

Offline CNK

  • Wiki Author
  • Sr. Member
  • *****
  • Posts: 289
Re: crond TCL version 11.1
« Reply #3 on: December 22, 2020, 11:11:38 PM »
The Wikipedia page for Cron describes @reboot as a non-standard definition, so it shouldn't be surprising if BusyBox doesn't support it.

Cronie is a crond implementation that supports it. There's no TCL extension for it, but maybe you could make one if you really need @reboot? Though don't forget about /opt/bootlocal.sh.

Offline mocallins

  • Newbie
  • *
  • Posts: 11
Re: crond TCL version 11.1
« Reply #4 on: December 23, 2020, 02:33:25 PM »
Hmmm, well i find references many places that it isn't supported, but nothing on the BusyBox site (busybox.net)
But then again some source code that shows it is implemented, however i don't know how it is implemetened in TinyCore.

I think whomever included it in TinyCore should do the lookup and find out if it is implemented.

I've done my due diligence to see if I'm doing everything correctly, and i feel that i have.
So now i'm reporting it.