George,
Thank you for the insight.
We've been running Samba as a PDC for Win2k clients for about seven months
and have experience only minor, and very infrequent, issues with file
locking under Samba 2.x and Linux Kernel 2.2.x (i.e., oplocks disabled).
In none of the issues in questions where files actually corrupted. Given
that I have a relatively small network (<30 machines) the probability of two
people using the same file at the same time are pretty small, so maybe I've
just been lucky.
>We were advised to disable oplocks by a lead member of the Samba team as
>i-bays enable concurrent updates from Samba, FTP and Appletalk.
I've been following the Samba Development mailing list for several months
and that always been the general advice of the gurus to those running Samba
on a version 2.2 kernel. When I questions John Terpstra about this, he told
me to enable oplocks even on a system that can't support OS file locking
(2.2 kernel). For the time being, I'm going to leave my system as is
(oplocks disables) and just keep an eye on things.
>Maybe you could run SWAT against our smb.conf, compare the output and
>report results? We don't normally recommend the use of SWAT as it (like
>webmin) is in direct conflict with our management of smb.conf through
>templates
The only thing that stuck me as a bit strange when I examined the e-smith
smb.conf template is that it defaults to roaming profiles. It is not
uncommon for Windows NT/Win2k profiles to be up to 500mb, or even more, in
size. Because of this I, and most of the MS network admins I know, user
local profiles. I find this very easy to implement in samba by setting the
follow parameters to a null (blank) setting: logon home, logon path, logon
drive.
Regards,
Greg
-----Original Message-----
From: Gordon Rowell [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 19 September 2001 11:44 PM
To: Greg J. Zartman, P.E.
Cc: [EMAIL PROTECTED]
Subject: Re: [e-smith-devinfo] Samba issues on e-smith
On Wed, Sep 19, 2001 at 01:44:27PM -0700, "Greg J. Zartman, P.E."
<[EMAIL PROTECTED]> wrote:
> Following is a conversation that I was involved with one of the Samba
> Developers. Does anyone have any insight on this issue with samba
> shares on a e-smith server?
> [...]
We were advised to disable oplocks by a lead member of the Samba team as
i-bays enable concurrent updates from Samba, FTP and Appletalk. We also
had an instance of file corruption at a client site which appeared to
be rectified by disabling oplocks.
We are actively discussing this issue with John Terpstra and other
members of the Samba team in order to find the appropriate solution.
Greg,
Maybe you could run SWAT against our smb.conf, compare the output and
report results? We don't normally recommend the use of SWAT as it (like
webmin) is in direct conflict with our management of smb.conf through
templates.
Thanks,
Gordon
--
Gordon Rowell [EMAIL PROTECTED]
VP Engineering
Network Server Solutions Group http://www.e-smith.com
Mitel Networks Corporation http://www.mitel.com
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
