Bug 84822
Summary: | Phoebe client takes over master browser/GC role on MS network | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Todd Booher <tbooher> |
Component: | samba | Assignee: | Jay Fenlason <fenlason> |
Status: | CLOSED RAWHIDE | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | bfox, djh, jfeeney, mitr |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-04-08 15:52:03 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Todd Booher
2003-02-21 18:36:23 UTC
The default configuration will never be appropriate for all environments. You need to set the browsing mastership appropriately for your network at the same time you change the workgroup name, server comment, etc. Instead of changing the default config, redhat-config-samba should have a convenient panel for setting these important parameters. I understand the default config will not meet everyone's particular layout but if it's left as is, it will create a problem with network services. I don't think Redhat want's to see a a new article about how some user placed their new Redhat pc on their corporate network and brought down a number of services. The changes I mentioned would still allow the user to browse the network, just not take control of it. Obviously, it's Redhat's decision, I just would hate to see it implemented like this since it will most likely cause people a great deal of pain. I agree with Todd...this default setting can cause problems with other computers on the network. We should always try to pick safe defaults. There should be a way to configure this in redhat-config-samba but I also think that we should try to pick defaults that will be right for the greatest number of users. I'm willing to bet that the majority of people running samba do not use is as the domain controller...they just want to share files with Windows machines. If this is true, then the majority of people using redhat-config-samba will have to go "unbreak" their configuration. We should make the common case as simple as possible. I changed the defaults for the next rawhide Samba build. Now I'll just have to field all the "Samba stopped working" bug reports from people who expect the old behavior. |