IHave you posted your crontab file here? It's weird that you say the crontab file is getting lost. Usually cron is started as a system service, so if you make any changes to crontab, it should always run...
On 4/27/06, Arne Gylseth <[EMAIL PROTECTED]> wrote:
Thanks for help/info !The command for help i think were "crontab --help"I were not able to use the editor under "crontab -e" but I used the crontab file variant, something like"crontab file /path/filename" , I think.Then I could edit the crontab file with another editor.Problem now:The crontab function now works for me, but I believe it will only be working until next reboot. Then it will get lost again.(Have not really checked yest, but I believe it will work this way.)The next issue is then to make the cronjob survive a reboot.Is ther a "last script thats run during startup" that could be used to initiate the cronjob ?( A last line "crontab file /path/filename" )Best reg Arne
_______________________________________________
Astlinux-users mailing list
[email protected]
http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED].
_______________________________________________ Astlinux-users mailing list [email protected] http://lists.kriscompanies.com/mailman/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to [EMAIL PROTECTED]
