Hello,
I configured the cron job as root using crontab -e, wrote the commands, and it’s also displayed with crontab -l.
Unfortunately, the configuration disappears after a reboot.
What’s causing this, and how can I prevent it?
Hello,
I configured the cron job as root using crontab -e, wrote the commands, and it’s also displayed with crontab -l.
Unfortunately, the configuration disappears after a reboot.
What’s causing this, and how can I prevent it?
I believe this behaviour is expected on ZimaOS. The system uses a mostly read-only system partition, so anything you add with crontab -e sits in an area that resets when the system reboots. That’s why your cron entries appear correctly, but disappear after a restart.
I think the reliable way to make scheduled tasks persistent on ZimaOS is to keep your scripts or automation inside the /DATA section, because /DATA is the only fully writable and permanent area. From there, you run your schedule through a small persistent app or container, since ZimaOS is designed so that apps handle all long-term configuration and storage.