Here's a one liner from the net that will remove the ^M from your configs.
Remember that a lot of Win editors will put them back in when you save
(UltraEdit has good support for DOS and Unix files).
perl -pi -e "s/\cM//g" filename
On Thu, 22 Mar 2001, Ryan wrote:
> I use slackware 7.1 and have hacked my smb.conf to pieces.. kinda
>
> the best part about using samba is seeing ^M all over the place when you use
> vi
> but yeah I'll try that net command.. learn something new everyday...
>
>
> -ryan
>
>
> ----- Original Message -----
> From: "Kevin Sangeelee" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Thursday, March 22, 2001 1:28 PM
> Subject: Re: Refresh
>
>
> > This is true, but it's possible to configure samba to cooperate nicely
> > with it's native file system. I'm not at work at the moment so I can't
> > check my files, but I think that rummaging around the docs on pessimistic
> > locking gets you close to the issues. I'm currently running samba/tomcat
> > on a RH6.2 box with more or less vanilla smb.conf, and it works perfectly.
> > The only time I had to reconfigure sambas locking settings (on a different
> > box) was when I needed a Unix program to detect write-locks held by a
> > samba client.
> >
> > Kevin
> >
> > On Thu, 22 Mar 2001, Craig R. McClanahan wrote:
> >
> > > On Thu, 22 Mar 2001, Ryan wrote:
> > >
> > > > Even so.. I've still had to 'touch' half the time. Though I access my
> JSP
> > > > code through windows via samba. Dunno if that has anything to do with
> it.
> > > >
> > >
> > > Yes, it absolutely does.
> > >
> > > Network file systems often cache directory information about the files
> you
> > > access, in order to avoid lots of network traffic. Thus, a file can be
> > > changed on the Samba server (with an updated timestamp), and the Samba
> > > client (i.e. the machine Tomcat is running on) does not know that.
> > >
> > > IMHO, running your webapps via a network file system (Windows shared
> > > disks, Samba, Unix NFS, etc.) is not a good idea. You'd be much better
> > > off (and have much better performance) if you moved Tomcat to where the
> > > files are located, rather than the other way around.
> >
>
>
