Steve Langasek wrote:
Ok. Can you confirm the version of the samba package installed on a machine
that's showing this problem, as send us the output of ls -l /var/lib/samba/
/var/cache/samba/ /var/run/samba/ on the affected machine?
It appears that after reinstalling the Debian Samba packages (I created
my own without the FHS patch), the problem does NOT reappear.
I'm having difficulties to understand this, as I completely removed
samba several times in the past month (dpkg --purge), reinstalled, put
my smb.conf back in place, and restarted samba. I always ended up with
only the master browser in my workgroup, untill I installed those
packages I made without the FHS patch. Now it all seems like it never
happened :/
There still is this other box in another workgroup however, where I also
installed those packages I made without the FHS patch to see if it would
solve the problem there. Even without the FHS patch, the workgroup that
box is master browser for, you never guess, only shows the master
browser. It had no problems with 3.0.20b-4. In addition, I reinstalled
the Debian Samba packages on this box too now (after dpkg --purge),
however the problem persists. Any advice welcome here...
In my network, there is yet another Debian Sid box, which is still
running Samba 3.0.20b-2. I'm quite confident that this box will show the
same problem if I do an apt-get (dist-)upgrade on it. I'm not trying it
however, as I've noticed there aren't any Debian Samba packages
available anymore < 3.0.21a (except those for Sarge ofcourse). If
someone can supply me with Debian Samba packages version 3.0.20b-4
however (the version I'm sure that did not show this problem), I will be
happy to do the test on this box, and mail you the results.
If the output from ls -l ... output is still wanted, please let me know
from which box(es) you would like to have it.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
