Re: *no crontab prob* [Was: Inquiry: How to set the crontab job permanently]
On Sun, 26 Jul 2009 04:48:15 -0500, Ron Johnson <ron.l.johnson@cox.net>
wrote:
> On 2009-07-26 02:38, Siggy Brentrup wrote:
>> On Sun, Jul 26, 2009 at 05:02 +0100, hadi motamedi wrote:
>>> Dear All
>>> We have set a new scheduled task through crontab job list , as the
>>> followings :
>>> #crontab -e
>>> 30 23 * * * cp ~www/db_backup/cdr/cdrFromMSC* /tmp
>>> It is functioning correctly but we will loose it after server reboot .
>>> Can
>>> you please let us know how we can set it permanently even after server
>>> reboot ?
>>
>> This is *not a crontab problem*
>>
>> Simply copy to a place that isn't
>> cleaned up upon boot. /tmp is intended for temporary storage, that's
>> why it's called /tmp.
>
> But who in ${DEITY}'s name puts crontab entries in /tmp???
>
I can find no mention anywhere in this thread that says the OP put crontab
entries in /tmp. The only reference to /tmp I see is the cp command
copying
stuff into /tmp. Am I missing something?
-- Kevin
Reply to: