Re: cifs 1.50 and dosemu 1.4 great combination

Claudia Neumann
2007-10-12T11:58:24Z

Hi Alain!

Yes, the newest samba and the newest cifs-code together with kernel > (I
think) 2.6.18 solves the samba locking problem. I just forgot to tell you.

At last my work and mails to Jeremy Allison were successful. Now even clipper
locks are recognized and reported to the clients. Nevertheless samba is very
slow. During my investigations about the samba locking problem I got the
advice to turn my network concept around. Now all my clients log in on the
server via ssh and start a dosemu or other session on the server. Network
trafic is very much reduced and the work on the clients is quicker than ever.
Working on Windows-servers/-clients can not keep up with that.

CU

Claudia Neumann

Am Freitag, 12. Oktober 2007 07:31 schrieb Alain M.:
> kemas escreveu:
> >> A clipper program runs on dosemu (I supose withe FreeDOS), dosemu runs
> >> on centos. But dosemu uses either an image (where lock work) or the
> >> linux fle system, I supose then that cifs is replacing samba and that
> >> lock work between doemu and cifs...
> >
> > cifs does not replace samba, samba still the file server.
> >
> > cifs is use as the filesystem to mount samba share, then dosemu would run
> > our program on lredired drive.
> > the lock here means file locking between multiuser apps that use the same
> > file.
>
> Could you give setup commands? This may interest more people, so I am
> bringing it back to the list...
>
> I am not sure that I understand: You have a samba server, maybe even on
> the same machine; cifs then replaces samba-client, on every machine;
> then dosemu relays the file-locks correctly. Are you using freeDOS?
>
> Sorry if I may seam a little dumb, but some time ago Bart said that lock
> did NOT work... and I googled about cifs and could not really understand
> the details.
>
> Thanks,
> Alain
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html