cron on 10.5.2 server

In article <bob-A32307.07492421042008@[199.45.49.11]>,
Robert Peirce <bob.DeleteThis@peirce-family.com.invalid> wrote:

> I still don¹t know how to create a crontab in the standard way.  Crontab
> ­e produces the following output:
>  
> $ crontab ­e
> create entry
> ZZ to exit
> crontab: no crontab for rbp - using an empty one
> crontab: temp file must be edited in place
>
> However, it works properly on my wife's 10.5.2 client and my 10.4.11
> client. Something seems not to be set correctly.

I experienced the same problem, and it was because I was using my
own install of Vim <http://www.vim.com>.

I solved my problem by defining a bash shell alias that makes sure
I'm using the Mac OS X provided vi (really Vim, but as provided by
Apple):

alias crontab='EDITOR=/usr/bin/vi /usr/bin/crontab'

This works every time, all the time.

Bob Harris
 >> Stay informed about: cron on 10.5.2 server 

In article <20080421194534.GC39909@fuchs>,
AndrÂŽ Berger <andre.berger.DeleteThis@web.de> wrote:

> * Robert Peirce (2008-04-21):
> > I still don¹t know how to create a crontab in the standard way.  Crontab
> > –e produces the following output:
> >  
> > $ crontab –e
> > create entry
> > ZZ to exit
> > crontab: no crontab for rbp - using an empty one
> > crontab: temp file must be edited in place
> >
> > However, it works properly on my wife's 10.5.2 client and my 10.4.11
> > client. Something seems not to be set correctly.
> >
> > I have found a work-around.
> >  
> > 1. Create a file of cron commands, cronfile.
> > 2. crontab cronfile
>
> I had to do a
>
> sudo ln -s /usr/lib/cron /var/
>
> and use
>
> EDITOR=nano crontab -e
>
> b/c I'm too lazy to figure out the correct vim options on
> Leopard/client

The problem is not with client. That works fine and as expected. The
problem is with server.

I can edit the file alright. It just doesn't get saved in the correct
location. /var/cron is not the solution, nor is the specific editor I use.

--
Robert B. Peirce, Venetia, PA 724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]
 >> Stay informed about: cron on 10.5.2 server 

* Bob Harris (2008-04-22):
> In article <bob-A32307.07492421042008@[199.45.49.11]>,
> Robert Peirce <bob.RemoveThis@peirce-family.com.invalid> wrote:
>
> > I still don¹t know how to create a crontab in the standard way.  Crontab
> > ­e produces the following output:
> >  
> > $ crontab ­e
> > create entry
> > ZZ to exit
> > crontab: no crontab for rbp - using an empty one
> > crontab: temp file must be edited in place
> >
> > However, it works properly on my wife's 10.5.2 client and my 10.4.11
> > client. Something seems not to be set correctly.
>
> I experienced the same problem, and it was because I was using my
> own install of Vim <http://www.vim.com>.
>
> I solved my problem by defining a bash shell alias that makes sure
> I'm using the Mac OS X provided vi (really Vim, but as provided by
> Apple):
>
> alias crontab='EDITOR=/usr/bin/vi /usr/bin/crontab'

I think one would have to ":set noswap" in vim

-André

--
May as well be hung for a sheep as a lamb!
Linkstation/KuroBox/HG/HS/Tera Kernel 2.6/PPC from <http://hvkls.dyndns.org>
 >> Stay informed about: cron on 10.5.2 server 

In article <nospam.News.Bob-0DCC6B.20021621042008 DeleteThis @news.verizon.net>,
Bob Harris <nospam.News.Bob DeleteThis @remove.Smith-Harris.us> wrote:

> In article <bob-A32307.07492421042008@[199.45.49.11]>,
> Robert Peirce <bob DeleteThis @peirce-family.com.invalid> wrote:
>
> > I still don¹t know how to create a crontab in the standard way.  Crontab
> > ­e produces the following output:
> >  
> > $ crontab ­e
> > create entry
> > ZZ to exit
> > crontab: no crontab for rbp - using an empty one
> > crontab: temp file must be edited in place
> >
> > However, it works properly on my wife's 10.5.2 client and my 10.4.11
> > client. Something seems not to be set correctly.
>
> I experienced the same problem, and it was because I was using my
> own install of Vim <http://www.vim.com>.
>
> I solved my problem by defining a bash shell alias that makes sure
> I'm using the Mac OS X provided vi (really Vim, but as provided by
> Apple):
>
> alias crontab='EDITOR=/usr/bin/vi /usr/bin/crontab'
>
> This works every time, all the time.
>
> Bob Harris

I just tried that and got the same

crontab: temp file must be edited in place

error. Something else is gong on here.

--
Robert B. Peirce, Venetia, PA 724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]
 >> Stay informed about: cron on 10.5.2 server 

In article <20080422050407.GD39909@fuchs>,
AndrÂŽ Berger <andre.berger.TakeThisOut@web.de> wrote:

> * Bob Harris (2008-04-22):
> > In article <bob-A32307.07492421042008@[199.45.49.11]>,
> > Robert Peirce <bob.TakeThisOut@peirce-family.com.invalid> wrote:
> >
> > > I still don¹t know how to create a crontab in the standard way.  Crontab
> > > –e produces the following output:
> > >  
> > > $ crontab –e
> > > create entry
> > > ZZ to exit
> > > crontab: no crontab for rbp - using an empty one
> > > crontab: temp file must be edited in place
> > >
> > > However, it works properly on my wife's 10.5.2 client and my 10.4.11
> > > client. Something seems not to be set correctly.
> >
> > I experienced the same problem, and it was because I was using my
> > own install of Vim <http://www.vim.com>.
> >
> > I solved my problem by defining a bash shell alias that makes sure
> > I'm using the Mac OS X provided vi (really Vim, but as provided by
> > Apple):
> >
> > alias crontab='EDITOR=/usr/bin/vi /usr/bin/crontab'
>
> I think one would have to ":set noswap" in vim

That is an "unknown option" in vi.

--
Robert B. Peirce, Venetia, PA 724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]
 >> Stay informed about: cron on 10.5.2 server 

In article <bob-B7DD2F.09320622042008@[199.45.49.11]>,
Robert Peirce <bob.TakeThisOut@peirce-family.com.invalid> wrote:

> In article <nospam.News.Bob-0DCC6B.20021621042008.TakeThisOut@news.verizon.net>,
> Bob Harris <nospam.News.Bob.TakeThisOut@remove.Smith-Harris.us> wrote:
>
> > In article <bob-A32307.07492421042008@[199.45.49.11]>,
> > Robert Peirce <bob.TakeThisOut@peirce-family.com.invalid> wrote:
> >
> > > I still don¹t know how to create a crontab in the standard way.  Crontab
> > > ­e produces the following output:
> > >  
> > > $ crontab ­e
> > > create entry
> > > ZZ to exit
> > > crontab: no crontab for rbp - using an empty one
> > > crontab: temp file must be edited in place
> > >
> > > However, it works properly on my wife's 10.5.2 client and my 10.4.11
> > > client. Something seems not to be set correctly.
> >
> > I experienced the same problem, and it was because I was using my
> > own install of Vim <http://www.vim.com>.
> >
> > I solved my problem by defining a bash shell alias that makes sure
> > I'm using the Mac OS X provided vi (really Vim, but as provided by
> > Apple):
> >
> > alias crontab='EDITOR=/usr/bin/vi /usr/bin/crontab'
> >
> > This works every time, all the time.
> >
> > Bob Harris
>
> I just tried that and got the same
>
> crontab: temp file must be edited in place
>
> error. Something else is gong on here.

When you are editing in vi/Vim, do you have a habit of doing

:w

I have that habit, and I've found that if I do that while editing
crontab files, it screws up crontab and I get a similar message to
what you are seeing.

I think the primary problem is if the editor creates a new file
(even if it has the same name) with a different file system inode
number, then crontab gets upset.

There are modes in Vim that can use the original as a backup file
and write an updated new file with the old name, or write the
updated information to a new file and when that is safely on disk,
do renames. I think it is this behavior that upsets crontab.

So maybe you need to comb through your .vimrc (or .exrc) to see if
there is any option causing this.

If you do have a .vimrc option to cause new files to be created,
try disabling it. If that works, but you like the option, then
create a script to invoke Vim with the -u NONE option, and invoke
this crontab with "EDITOR=your_script crontab -e"

Bob Harris
 >> Stay informed about: cron on 10.5.2 server 

* Robert Peirce (2008-04-22):
> In article <20080422050407.GD39909@fuchs>,
> AndrÂŽ Berger <andre.berger.DeleteThis@web.de> wrote:
>
> > * Bob Harris (2008-04-22):
> > > In article <bob-A32307.07492421042008@[199.45.49.11]>,
> > > Robert Peirce <bob.DeleteThis@peirce-family.com.invalid> wrote:
[...]
> > > > crontab: temp file must be edited in place
[...]
> > > I solved my problem by defining a bash shell alias that makes sure
> > > I'm using the Mac OS X provided vi (really Vim, but as provided by
> > > Apple):
> > >
> > > alias crontab='EDITOR=/usr/bin/vi /usr/bin/crontab'
> >
> > I think one would have to ":set noswap" in vim
>
> That is an "unknown option" in vi.

That's why I wrote "vim" :)

-André

--
May as well be hung for a sheep as a lamb!
Linkstation/KuroBox/HG/HS/Tera Kernel 2.6/PPC from <http://hvkls.dyndns.org>
 >> Stay informed about: cron on 10.5.2 server 

In article <nospam.News.Bob-435213.19554022042008.RemoveThis@news.verizon.net>,
Bob Harris <nospam.News.Bob.RemoveThis@remove.Smith-Harris.us> wrote:

> In article <bob-B7DD2F.09320622042008@[199.45.49.11]>,
> Robert Peirce <bob.RemoveThis@peirce-family.com.invalid> wrote:
>
> > In article <nospam.News.Bob-0DCC6B.20021621042008.RemoveThis@news.verizon.net>,
> > Bob Harris <nospam.News.Bob.RemoveThis@remove.Smith-Harris.us> wrote:
> >
> > > In article <bob-A32307.07492421042008@[199.45.49.11]>,
> > > Robert Peirce <bob.RemoveThis@peirce-family.com.invalid> wrote:
> > >
> > > > I still don¹t know how to create a crontab in the standard way. 
> > > > Crontab
> > > > ­e produces the following output:
> > >
> > > I experienced the same problem, and it was because I was using my
> > > own install of Vim <http://www.vim.com>.
> > >
> > > I solved my problem by defining a bash shell alias that makes sure
> > > I'm using the Mac OS X provided vi (really Vim, but as provided by
> > > Apple):
> > >
> > > alias crontab='EDITOR=/usr/bin/vi /usr/bin/crontab'
> > >
> > > This works every time, all the time.
> > >
> > > Bob Harris
> >
> > I just tried that and got the same
> >
> > crontab: temp file must be edited in place
> >
> > error. Something else is going on here.
>
> When you are editing in vi/Vim, do you have a habit of doing
>
> :w

I don't think that is the issue. Crontab -e used to work before we
re-installed the OS. Something got changed, but I don't know what.

--
Robert B. Peirce, Venetia, PA 724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]
 >> Stay informed about: cron on 10.5.2 server 

In article <bob-391647.07280423042008@[199.45.49.11]>,
Robert Peirce <bob.TakeThisOut@peirce-family.com.invalid> wrote:

> Crontab -e used to work before we
> re-installed the OS. Something got changed, but I don't know what.

It may be you have a corrupt / incomplete install.

Did you upgrade, by chance?

--
Please send all responses to the relevant news group. E-mail sent to
this address may be devoured by my very hungry SPAM filter. I do not
read posts from Google Groups. Use a real news reader if you want me to
see your posts.

JR
 >> Stay informed about: cron on 10.5.2 server 

On Wed, 23 Apr 2008 06:45:51 +0200, André Berger wrote:
> * Robert Peirce (2008-04-22):
>> In article <20080422050407.GD39909@fuchs>,
>> AndrÂ? Berger <andre.berger.RemoveThis@web.de> wrote:
>>
>> > * Bob Harris (2008-04-22):
>> > > In article <bob-A32307.07492421042008@[199.45.49.11]>,
>> > > Robert Peirce <bob.RemoveThis@peirce-family.com.invalid> wrote:
> [...]
>> > > > crontab: temp file must be edited in place
> [...]
>> > > I solved my problem by defining a bash shell alias that makes sure
>> > > I'm using the Mac OS X provided vi (really Vim, but as provided by
>> > > Apple):
>> > >
>> > > alias crontab='EDITOR=/usr/bin/vi /usr/bin/crontab'
>> >
>> > I think one would have to ":set noswap" in vim
>>
>> That is an "unknown option" in vi.

> That's why I wrote "vim" :)

It's an "unknown option" in /usr/bin/vim, at least under OS X 10.5.2
client.



--
Dave Seaman
Third Circuit ignores precedent in Mumia Abu-Jamal ruling.
<http://www.indybay.org/newsitems/2008/03/29/18489281.php>
 >> Stay informed about: cron on 10.5.2 server 

In article <jollyroger-2ECE6F.08451323042008 RemoveThis @individual.net>,
Jolly Roger <jollyroger RemoveThis @pobox.com> wrote:

> In article <bob-391647.07280423042008@[199.45.49.11]>,
> Robert Peirce <bob RemoveThis @peirce-family.com.invalid> wrote:
>
> > Crontab -e used to work before we
> > re-installed the OS. Something got changed, but I don't know what.
>
> It may be you have a corrupt / incomplete install.
>
> Did you upgrade, by chance?

Our consultant was messing with the system and got it to a state where
we had to restore from a SuperDuper backup. I agree something seems to
be corrupt, but I can't figure out what. Unfortunately, I have no idea
how to interpret the error message. What does it mean that the file
must be edited in place?

--
Robert B. Peirce, Venetia, PA 724-941-6883
bob AT peirce-family.com [Mac]
rbp AT cooksonpeirce.com [Office]
 >> Stay informed about: cron on 10.5.2 server 

On 2008-04-23 15:46:54 +0100, Robert Peirce
<bob.RemoveThis@peirce-family.com.invalid> said:

> In article <jollyroger-2ECE6F.08451323042008.RemoveThis@individual.net>,
> Jolly Roger <jollyroger.RemoveThis@pobox.com> wrote:
>
>> In article <bob-391647.07280423042008@[199.45.49.11]>,
>> Robert Peirce <bob.RemoveThis@peirce-family.com.invalid> wrote:
>>
>>> Crontab -e used to work before we
>>> re-installed the OS. Something got changed, but I don't know what.
>>
>> It may be you have a corrupt / incomplete install.
>>
>> Did you upgrade, by chance?
>
> Our consultant was messing with the system and got it to a state where
> we had to restore from a SuperDuper backup. I agree something seems to
> be corrupt, but I can't figure out what. Unfortunately, I have no idea

I think you have to tell the consultant to fix what he's broken.
There's a reason you're paying them mega bucks, eh?

> how to interpret the error message. What does it mean that the file
> must be edited in place?

Basically, are the contents of the existing file changing (edited in
place) or is a new file being created and given the old file's name.

In pseudo-code, is this happening:

open existing file for read/write
read everything
overwrite with different stuff
close file

or this:

open existing file for read
read everything
close file
open new file for write
write different stuff
close new file
delete existing file
rename new file as existing file

Cheers,

Chris
 >> Stay informed about: cron on 10.5.2 server 

* Dave Seaman (2008-04-23):
> On Wed, 23 Apr 2008 06:45:51 +0200, André Berger wrote:
> > * Robert Peirce (2008-04-22):
> >> In article <20080422050407.GD39909@fuchs>,
> >> AndrÂ? Berger <andre.berger.DeleteThis@web.de> wrote:
> >>
> >> > * Bob Harris (2008-04-22):
> >> > > In article <bob-A32307.07492421042008@[199.45.49.11]>,
> >> > > Robert Peirce <bob.DeleteThis@peirce-family.com.invalid> wrote:
> > [...]
> >> > > > crontab: temp file must be edited in place
> > [...]
> >> > > I solved my problem by defining a bash shell alias that makes sure
> >> > > I'm using the Mac OS X provided vi (really Vim, but as provided by
> >> > > Apple):
> >> > >
> >> > > alias crontab='EDITOR=/usr/bin/vi /usr/bin/crontab'
> >> >
> >> > I think one would have to ":set noswap" in vim
> >>
> >> That is an "unknown option" in vi.
>
> > That's why I wrote "vim" :)
>
> It's an "unknown option" in /usr/bin/vim, at least under OS X 10.5.2
> client.

Ouch, it's ":set noswapfile", sorry!

-André

--
May as well be hung for a sheep as a lamb!
Linkstation/KuroBox/HG/HS/Tera Kernel 2.6/PPC from <http://hvkls.dyndns.org>
 >> Stay informed about: cron on 10.5.2 server