I had this exact problem. As best as I was able to figure it out, it
was caused by the upgrade to CentOS 4.4. A few of the files from the
cron RPM didn't work right under the SELinux, I had to do a restoreconf
to all the files in the cron RPM and then all was OK. I have no idea
why this happened.
Matt
Ian mu wrote:
Actually it seems to be the same now even when I dos2unix now (seems
to work sometimes not others which is confusing me even more now),
wondering if its selinux after all even though afaik it shouldn't be.
On 9/25/06, *Ian mu* <mu.llamas@xxxxxxxxx
<mailto:mu.llamas@xxxxxxxxx>> wrote:
Hiya, thanks again, there's no .vimrc file at all.
:set gives
:set
--- Options ---
backspace=2 history=50 scroll=11 ttyfast
fileencodings=ucs-bom,utf-8,latin1
Hit ENTER or type command to continue
This is exactly the same as in crontab -e (thats what I use to
edit anyway though, so assume it just calls vim), it was also the
same problem in nano when I tried after you mentioned that.
Thanks, Ian
On 9/25/06, *Will McDonald* <wmcdonald@xxxxxxxxx
<mailto:wmcdonald@xxxxxxxxx>> wrote:
On 25/09/06, Ian mu < mu.llamas@xxxxxxxxx
<mailto:mu.llamas@xxxxxxxxx>> wrote:
> Hiya, thanks a lot for that Will (sorry spelt name wrong
before!), think
> you're reply has almost got there...
>
> If I dos2unix the file it works, if I use vi/m (what I
normally use) or nano
> etc, it doesn't work (but will if I then dos2unix it again)?
>
> SELinux I think is on permissive/targeted (I'm not too
familiar with selinux
> as someone else set it up, but my understanding is that it
should allow all,
> but log/audit it?).
>
> Looks like thats it, but not sure still why its not saving it
correctly?
Sounds like vi/vim's doing something weird to the file on
write/save.
Have you any user specific initialisation in the user whose
crontab
you're editing's $HOME? i.e. If you're setting up the crontab for
logadmin, whilst logged in *as* logadmin, is there a
$HOME/.vimrc file
or similar?
If you just run vi/vim without passing it any files to edit
then do
:set
... what does that result it? On a vanilla system here with
vim-enhanced installed and no customisations, running vi I get...
:set
--- Options ---
backspace=2 history=50 ttyfast
t_Sf=^[[3%dm
cscopetag hlsearch ttymouse=xterm
cscopeverbose ruler viminfo='20,"50
helplang=en scroll=11 t_Sb=^[[4%dm
cscopeprg=/usr/bin/cscope
fileencodings=utf-8,latin1
Hit ENTER or type command to continue
Compare that to what you get by default and what you get when
you run
crontab -e. If I run crontab -e then examine vi's environment it's
just...
:set
--- Options ---
backspace=2 history=50 scroll=11
ttyfast
fileencoding=utf-8
fileencodings=ucs-bom,utf-8,latin1
Hit ENTER or type command to continue
Will.
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx <mailto:CentOS@xxxxxxxxxx>
http://lists.centos.org/mailman/listinfo/centos
------------------------------------------------------------------------
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
