https://bugzilla.novell.com/show_bug.cgi?id=378988
User alpha096@virginbroadband.com.au added comment
https://bugzilla.novell.com/show_bug.cgi?id=378988#c6
Scott Couston changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|alpha096@virginbroadband.com.au |
--- Comment #6 from Scott Couston 2008-06-10 17:11:23 MDT ---
Yes, this is a bug, however there more I watch what establishing a Samba Server
does, the more the process becomes confused.
1. Once a Samba Server is created, instead, of requesting an election between
itself and the other Windows Workgroup members -It demands that the samba
server IS the Master Browser - I can find no logic in this demand.
I can also find no logic in YAST of Both creating a Samba Server, which
established the workgroup (same as other Windows PC's), to the other
functionality in Yast which solely joins a Linux PC to a Workgroup or Domain.
I can also find no logic in the 2 x different yast services which both
establish the same workgroup or domain - The only difference in one (Join a
Domain or Workgroup) is that a Samba Server is not started.
Again I find no logic in this sole function as it is duplicated in starting a
Samba Server.
What logic is there in Yast for a Linux PC Soley Joining a Workgroups or Domain
when at all times this achieves nothing but to complicate the issue and with
both function permits even more possible discrepancies between adhering to the
same workgroups name of domain name.
The log which is attached IS the Samba Log, however to ease you viewing of the
log it can we formatted nicely for inspection by Ksystem Log.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.