Re: [foxboro] crontab AP51D V6.1

Try this;
cd /your_favorite_place_to_put_stuff
crontab -l >cronfile
cp cronfile cronfile.bak
vi cronfile
fix it up the way u like it, save it and
crontab cronfile

now you have a backup file (cronfile.bak), a copy of the current (cronfile) 
and the master cronfile has been changed and activated when you issued 
'crontab cronfile'.

----- Original Message ----- 
From: "Ron Deen" <r.deen@xxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Sent: Friday, October 29, 2004 11:52 AM
Subject: Re: [foxboro] crontab AP51D V6.1


> To add even one more:
>
> With "crontab -e" you edit the crontab for the current user, by default 
> the
> "editor" ed is used however and not out beloved vi.
> To change that:
> In the bourne shell
> # EDITOR=vi ; export EDITOR
> and you are done
>
> In the C-shell:
> # setenv EDITOR vi
> and you done here too.
> May be an idea to change this in you environment file (.profile or .cshrc)
>
> MAKE BACKUPS as standard procedure ;-)
>
> Have a good weekend all,
>
> Regards
>
> Ron Deen
> Invensys
>
> On Friday 29 October 2004 15:02, Jaudon, Michael wrote:
>> To add to what Duc stated...
>>
>> To be super safe you might want to copy "crontempfile" to
>> "crontempfile.bak".
>>
>> Then VI "crontempfile".
>>
>> #crontab crontempfile
>>
>> If anything goes wrong you will have your original crontab file in
>> "crontempfile.bak"
>>
>> This is just a suggestion.  Sometimes you learn the hard way.
>>
>> Michael L. Jaudon
>> Kerr-McGee Chemical LLC
>> (662)343-8710 Office
>> (662)304-0313 Cell
>> mjaudon@xxxxxxx
>>
>> If you are not the intended recipient of this e-mail message, any use,
>> distribution or copying of the message is prohibited.  Please let me
>> know immediately by return e-mail if you have received this message by
>> mistake, then delete the e-mail message.  Thank you.
>>
>>
>>
>> -----Original Message-----
>> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
>> On Behalf Of duc.do@xxxxxxxxxxxxxx
>> Sent: Friday, October 29, 2004 7:20 AM
>> To: foxboro@xxxxxxxxxxxxx
>> Subject: Re: [foxboro] crontab AP51D V6.1
>>
>>
>> While your suggestion of using -e to edit the crontab table is a valid =
>> =3D
>> one, I prefer to make my mistake in a temporary file. ;-)
>>
>> crontab -l > crontempfile
>> vi crontempfile
>>
>> When you're ready to effect the change(s) to the cron table, run:
>>
>> crontab < crontempfile
>>
>> Duc
>>
>> --=3D20
>> Duc M. Do
>> Dow Corning Corp.
>> Carrollton Plant
>> Carrollton, KY, US
>>
>>
>> -----Original Message-----
>> From: foxboro-bounce@xxxxxxxxxxxxx
>> [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Lieven Taleman
>> Sent: Friday, October 29, 2004 7:26 AM
>> To: foxboro@xxxxxxxxxxxxx
>> Subject: Re: [foxboro] crontab AP51D V6.1
>>
>> On your Unix box in a VT100 terminal (as user root) type :
>> > man crontab   # With this you will find all necessary information to
>>
>> manage your cron.
>>
>> > crontab -e    # This one opens a VI editor to make your changes
>> > crontab -l    # Verify your changes
>>
>> Greetings,
>> Lieven Taleman
>> B.V.B.A TALSOFT - Belgium
>> E-mail : lieven.taleman@xxxxxxxxxx
>>
>> -----Oorspronkelijk bericht-----
>> Van: foxboro-bounce@xxxxxxxxxxxxx
>> [mailto:foxboro-bounce@xxxxxxxxxxxxx]Namens Mougeot, Thierry T SPM-SMUC
>> Verzonden: vrijdag 29 oktober 2004 13:08
>> Aan: Cassandra Foxboro (E-mail)
>> Onderwerp: [foxboro] crontab AP51D V6.1
>>
>>
>> Hi list ,
>> I don't remember the way to change a crontab file . What procedure must
>> =3D one follow to change this file ? Thanks
>>
>>
>> Salutations
>> MOUGEOT Thierry
>> Secteur SMUC Utilites Chimie AT I/E CNC
>> Shell P=3DE9trochimie M=3DE9diterran=3DE9e
>> BP 14, 13131  Berre l'=3DE9tang, Cedex, France
>> Tel: +33 4 42 74  57 03 Fax: 54 20
>> Email: Thierry.Mougeot@xxxxxxxxx
>> Internet: http://www.shell.com/chemicals
>>
>> =20
>> =20
>> _______________________________________________________________________
>> This mailing list is neither sponsored nor endorsed by Invensys Process
>> Systems (formerly The Foxboro Company). Use the info you obtain here at
>> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>> =20
>> foxboro mailing list:             http://www.freelists.org/list/foxboro
>> to subscribe:         =
>> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
>> to unsubscribe:      =
>> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
>> =20
>>
>>
>> _______________________________________________________________________
>> This mailing list is neither sponsored nor endorsed by Invensys Process
>> Systems (formerly The Foxboro Company). Use the info you obtain here at
>> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>>
>> foxboro mailing list:             http://www.freelists.org/list/foxboro
>> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
>> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>
>
> _______________________________________________________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>
> foxboro mailing list:             http://www.freelists.org/list/foxboro
> to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
> 


 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: