Your message dated Tue, 5 Jun 2007 18:57:14 +0200
with message-id <[EMAIL PROTECTED]>
and subject line I'm quite certain this bug is now fixed
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: samba
Version: 3.0.0final-1
Severity: normal
hi folks....
unfortunately, i can only give you 2nd-hand info, because i usually do not
have access to the machine/network i am reporting about:
the server just upgraded from woody to sarge and thus samba 3.0.0final-1
was installed. now the Win2K client does not show all files in the
home-directory of the accessing user which it did before with version 2.2.3.
the home-directory contains about 500+ files/directories. i assume that
it does not matter if the directory in question is the home-directory or
any other beneath it.
new directories can be created but they fail to be displayed on the
client, though the new one exists as can be seen in a shell on the
server.
we also realised that moving some dirs/files around, thus reducing the
total amount of items to be displayed, actually helps. the threshold could
be 512 or so.
there does not seem to be a parameter in smb.conf to adjust that number,
so it seems that it is either "unlimited" (or better
/proc/sys/fs/file-max) or defined somewhere in the sources to a
relatively low number. though i found some rather old manual at
http://www.os9samba.com/manual.html which talks about
max-files-per-directory.
well, this should describe the problem fair enough. btw, there was
nothing to be found about such a problem on the net (debian-ml,
debian-bugs, google) which kind of surprises me.
i can supply the smb.conf and a log (level 3) of a session if needed.
cheers,
sebastian
-- System Information:
Debian Release: sarge
Architecture: i386
Kernel: Linux enigma 2.4.22-pre6-sh #4 Die Jul 15 20:06:08 CEST 2003 i686
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8
Versions of packages samba depends on:
ii debconf 1.3.15 Debian configuration management sy
ii libacl1 2.2.20-1 Access control list shared library
ii libc6 2.3.2.ds1-10 GNU C Library: Shared libraries an
ii libcomerr2 1.34+1.35-WIP-2003.08.21-3 The Common Error Description libra
ii libcupsys2 1.1.19final-1.4 Common UNIX Printing System(tm) -
ii libgnutls7 0.8.9-2 GNU TLS library - runtime library
ii libkrb53 1.3-2 MIT Kerberos runtime libraries
ii libldap2 2.1.22-1 OpenLDAP libraries
ii libpam-module 0.76-14 Pluggable Authentication Modules f
ii libpam-runtim 0.76-14 Runtime support for the PAM librar
ii libpam0g 0.76-14 Pluggable Authentication Modules l
ii libpopt0 1.7-2 lib for parsing cmdline parameters
ii logrotate 3.6.5-2 Log rotation utility
ii netbase 4.14 Basic TCP/IP networking system
ii samba-common 3.0.0final-1 Samba common files used by both th
-- debconf information excluded
--- End Message ---
--- Begin Message ---
We went on several such bugs two years ago while triaging the bugs in
the samba package.
These were since fixed upstream but I can't exactly tell when..:-)
Please reopen if you still experience the issue but I'm quite sure you
don't.
--
signature.asc
Description: Digital signature
--- End Message ---
