Quoting John H Terpstra ([EMAIL PROTECTED]):
> Christian,
>
> I will gladly document this bug. Please would you forward details to assist
> me
> to describe this fully.
The bug submitter (David Fokkema, CC'ed to this mail) reported first:
====================================================
Since version 3.0.4-1 (3.0.2a-1 is ok) I do no longer see my printer
share listed when I run `smbclient -L servername'. I can still connect
to it, but I have to know there is a print share beforehand. I tried
several options in smb.conf, but I could not get it right. Since a
simple upgrade caused this behaviour, I consider it a bug. And since
Sarge is shipping next week I consider it important. Maybe not...
I noticed this bug when upgradeing from 2.2.5-1 to 3.0.14a-1.
Anyway, this is my swat-generated smb.conf:
# Samba config file created using SWAT
# from 192.168.20.20 (192.168.20.20)
# Date: 2005/05/24 09:41:39
# Global parameters
[global]
workgroup = ILEOS
printcap name = cups
ldap ssl = no
panic action = /usr/share/samba/panic-action %d
printing = cups
print command =
lpq command = %p
lprm command =
[printers]
comment = All Printers
path = /tmp
printable = Yes
[homes]
comment = Home Directories
valid users = %S
read only = No
browseable = No
=====================================================
Then, later:
I'm so sorry. This has been addressed in bug 1644 on bugzilla.samba.org.
See https://bugzilla.samba.org/show_bug.cgi?id=1644 . The problem is
that the CUPS name for my printer was longer than 12 characters. Somehow
this breaks samba > 3.0.2a. As stated on samba.org, this won't be fixed.
Please, could you include this in README.Debian? Thanks for not flaming
me.
======================================================
So far, it seems that the problem can be resumed to "smbd doesn't show
share names with more than 12 characters to smbclient". So, this is an
issue for smbclient connecting to a samba server (or the local server).
Details and discussion are in Samba bug 1644 as mentioned.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
