Your message dated Tue, 15 Sep 2009 08:09:40 -0700
with message-id <[email protected]>
and subject line Re: Bug#182970: samba-common: smbpasswd complains about
missing unexpected.tdb
has caused the Debian Bug report #182970,
regarding samba-common: smbpasswd complains about missing unexpected.tdb
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
182970: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=182970
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: samba-common
Version: 2.2.3a-12
Severity: minor
Hello
I have some debian boxes that I installed samba-common on, so that the
users could update their NT passwords, from unix. I have no intention
of running smbd or nmbd on these boxes, we have those services on other
hosts in our network.
The complaint I have may be upstream's problem, or it may be a postinstall
debian issue. When I installed samba-common, I didn't edit smb.conf, but
just tried running nmblookup:
bar% nmblookup -M -T foo
querying foo on xxx.xxx.xxx.xxx
tdb((null)): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb:
No
such file or directory
tdb((null)): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb:
No
such file or directory
tdb((null)): tdb_open_ex: could not open file /var/run/samba/unexpected.tdb:
No
such file or directory
ding.dong.dell, xxx.xxx.xxx.xxx foo<1d>
I get a valid domain controller name and IP address back, so the
tdb messages don't seem to cause any real problems. But unexpected.tdb
seems to have a real function (storing packets sent to wrong ports by
MS machines with borken configs). So should the post-install create
an empty one, with the right permissions? It seems possible to do this
independent of any other configuration that is required, and it would
make the 'client-only' use I describe here a bit nicer.
I have strace output if you want to look into this further.
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux bar 2.4.18-686-smp #1 SMP Sun Apr 14 12:07:19 EST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages samba-common depends on:
ii debconf 1.0.32 Debian configuration management sy
ii libc6 2.2.5-11.2 GNU C Library: Shared libraries an
ii libcupsys2 1.1.14-4.4 Common UNIX Printing System(tm) -
ii libpam-modules 0.72-35 Pluggable Authentication Modules f
ii libpam0g 0.72-35 Pluggable Authentication Modules l
--- End Message ---
--- Begin Message ---
On Tue, Sep 15, 2009 at 04:32:57AM -0400, Andrew Schulman wrote:
> I have this bug with samba-common 2:3.4.0-5.
Because you're using a non-default 'debug level' setting in your smb.conf.
You asked for debugging and you got it. No bug here.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
[email protected] [email protected]
signature.asc
Description: Digital signature
--- End Message ---
