Under Unix/linux, the easiest way to get rid of them is as follows: tr -d "\r" <squidGuard.conf >squidGuard.conf.new
-Karl On Monday 15 March 2004 15:01, you wrote: > This is usual windows returns and crlf and unix returns are just lf (or > is it cr I never remeber). > > There are 2 ways to fix this is one of the easiest is if you are using > > vim (not just plain vi) open the file then in command mode type: > :set fileformat=unix > :w > > This should help. > > I suspect your using plain vi, in which case try (in command mode) > > :%s/CTRL-VCTRL-M$// > > Thats press CONTROL and V then CONTROL and M. > > That might clear the ^M's for and perhaps repair parsing errors. > > Regards, > > Stewart James > > On Tue, 2004-03-16 at 08:30, [EMAIL PROTECTED] wrote: > > Most likely. Next time, when you ftp it, be sure you specify ASCII mode > > transfer, before you put the file. > > > > TimR > > > > > > > > > > Ryan Nix <[EMAIL PROTECTED]> > > Sent by: [EMAIL PROTECTED] > > 03/15/2004 03:07 PM > > > > To: [EMAIL PROTECTED] > > cc: > > Subject: ^M > > > > > > I seem to have a lot of ^M in my conf file when I edit it through vi. > > Yes, I was editing through Notepad on Windows. > > > > Is this why I would be receiving the parse line one error?
