my crontab entries disappear after a reboot

[dave14305]

Sorry @dvohwinkel I gave you bad advice. I should have double-checked.

init-start is too early in the boot process, you should be using services-start.

I'm happy to argue that you're wrong in being wrong, since amtm also uses init-start for the reboot scheduler script.

 

[dvohwinkel]

I'm happy to argue that you're wrong in being wrong, since amtm also uses init-start for the reboot scheduler script.

From the wiki..

init-start
Called right after JFFS got mounted, and before any of the services get started. This is the earliest part of the boot process where you can insert something.

That might be too soon for logger to show up.. and if cron is not running yet.. hmmm..

 

[dave14305]

From the wiki..

init-start
Called right after JFFS got mounted, and before any of the services get started. This is the earliest part of the boot process where you can insert something.

That might be too soon for logger to show up.. and if cron is not running yet.. hmmm..

Instead of logger, add a command like this:

touch /tmp/init-start-ran-ok

And see if it's there after a reboot. It won't have a valid timestamp since it's before time is synced, but you'll know it ran the script. You can't go wrong with services-start either, but init-start isn't technically wrong.

 

[ColinTaylor]

ahh I was starting to wonder that Thank you so much for checking. I will test it in a little bit.

Probably a sign of old age. My brain was thinking one thing and my fingers were typing something else.

I'm happy to argue that you're wrong in being wrong, since amtm also uses init-start for the reboot scheduler script.

Interesting. Maybe it's because amtm uses cru.

That might be too soon for logger to show up.. and if cron is not running yet.. hmmm..

It's too early for logger. I think using cru makes it wait.

 

[dave14305]

Interesting. Maybe it's because amtm uses cru.

Yes, that can be the only viable explanation now. cru adds to a <user>.new file, and when crond starts it seems to recreate the actual crontabs.

 

[dvohwinkel]

Yes, that can be the only viable explanation now. cru adds to a <user>.new file, and when crond starts it seems to recreate the actual crontabs.

So even moving it to services-start didn't work. What did work was using "cru a" .. so both @dave14305 and @ColinTaylor were both right
What a journey of discovery I'm sure my family will be glad the internet stops going away
Thank you both for all the help!

 

[dave14305]

So even moving it to services-start didn't work. What did work was using "cru a" .. so both @dave14305 and @ColinTaylor were both right
What a journey of discovery I'm sure my family will be glad the internet stops going away
Thank you both for all the help!

As my wife might say to me, I now say to you (just to see what it feels like): “If you would have listened to me in post #7, all this could have been avoided!”