<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.3314" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>Package:
samba</FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>Version:
3.0.24-6etch9</FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>Linux phone
2.6.18-6-686 #1 SMP Sun Feb 10 22:11:31 UTC 2008 i686 GNU/Linux<BR>libc6
version: 2.3.6.ds1-13etch5<BR></FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>The following email
is sent several times a day, I have not been able to isolate any specific event
in the office to cause this:</FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>The Samba 'panic
action' script, /usr/share/samba/panic-action,</FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>was called for PID
10866 (/umbd).</FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>This means there was
a problem with the program, such as a segfault.</FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>sr/sbin/sBelow is a
backtrace for this process generated with gdThe Samba 'panic action' script,
/usr/share/samba/panic-action,<BR>was called for PID 10866
(/usr/sbin/smbd).</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>This means there was
a problem with the program, such as a segfault.<BR>Below is a backtrace for this
process generated with gdb, which shows<BR>the state of the program at the time
the error occurred. The Samba log<BR>files may contain additional
information about the problem.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>If the problem
persists, you are encouraged to first install the<BR>samba-dbg package, which
contains the debugging symbols for the Samba<BR>binaries. Then submit the
provided information as a bug report to<BR>Debian. For information about
the procedure for submitting bug reports,<BR>please see <A
href="http://www.debian.org/Bugs/Reporting">http://www.debian.org/Bugs/Reporting</A>
or the reportbug(1)<BR>manual page.</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>Using host
libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".<BR>[Thread
debugging using libthread_db enabled]<BR>[New Thread -1213294912 (LWP
10866)]<BR>0xb7f0a410 in ?? ()<BR>#0 0xb7f0a410 in ?? ()<BR>#1
0x00000001 in ?? ()<BR>#2 0x00000000 in ?? ()</FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>I have installed the
samba-dbg package, perhaps I need to do something to activate
it?</FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>The only
particularly odd thing that I can think of is the rather constant presence in
the logs of messages like:</FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2>log.tophers-compute.old:[2008/04/25 14:54:04, 0]
auth/auth_util.c:create_builtin_administrators(785)<BR>log.tophers-compute.old:
create_builtin_administrators: Failed to create
Administrators<BR>log.tophers-compute.old:[2008/04/25 14:56:03, 0]
auth/auth_util.c:create_builtin_administrators(785)<BR>log.tophers-compute.old:
create_builtin_administrators: Failed to create
Administrators<BR></FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>Though these
messages have been there for a least a year, and the panic action is a recent
development. I'm afraid that I can't tell you exactly when it started,
though the first email I have saved, which may have been the first one was on
April 10</DIV></FONT></SPAN>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2> </DIV></FONT></SPAN>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>Below is my
smb.conf</FONT></SPAN></DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2>#======================= Global Settings
=======================</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial
size=2>[global]</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>##
Browsing/Identification ###<BR> netbios name = MUIR<BR># Change this
to the workgroup/NT-domain name your Samba server will part of<BR>
workgroup = GREENBLUE</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># server string is
the equivalent of the NT Description field<BR> server string = %h
server</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># Windows Internet
Name Serving Support Section:<BR># WINS Support - Tells the NMBD component of
Samba to enable its WINS Server<BR> wins support =
yes</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># WINS Server -
Tells the NMBD components of Samba to be a WINS Client<BR># Note: Samba can be
either a WINS Server, or a WINS Client, but NOT both<BR>; wins
server = w.x.y.z</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># If we receive WINS
server info from DHCP, override the options above. <BR># include =
/etc/samba/dhcp.conf</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># This will prevent
nmbd to search for NetBIOS names through DNS.<BR> dns proxy =
no</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># What naming
service and in what order should we use to resolve host names<BR># to IP
addresses<BR> name resolve order = lmhosts wins hosts
bcast</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>#### Networking
####</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># The specific set
of interfaces / networks to bind to<BR># This can be either the interface name
or an IP address/netmask;<BR># interface names are normally
preferred<BR> interfaces = 127.0.0.1 lo eth0 eth2
eth0:0</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># Only bind to the
named interfaces and/or networks; you must use the<BR># 'interfaces' option
above to use this.<BR># It is recommended that you enable this feature if your
Samba machine is<BR># not protected by a firewall or is a firewall itself.
However, this<BR># option cannot handle dynamic or non-broadcast interfaces
correctly.<BR> bind interfaces only = true</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>####
Debugging/Accounting ####</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># This tells Samba
to use a separate log file for each machine<BR># that connects<BR>
log file = /var/log/samba/log.%m<BR> debug level = 5<BR># Put a
capping on the size of the log files (in Kb).<BR> max log size =
1000</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># If you want Samba
to only log through syslog then set the following<BR># parameter to
'yes'.<BR>; syslog only = no</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># We want Samba to
log a minimum amount of information to syslog. Everything<BR># should go to
/var/log/samba/log.{smbd,nmbd} instead. If you want to log<BR># through syslog
you should set the following parameter to something higher.<BR>
syslog = 0</FONT></SPAN></DIV>
<DIV> </DIV>
<DIV><SPAN class=600214818-30042008><FONT face=Arial size=2># Do something
sensible when Samba crashes: mail the admin a backtrace<BR> panic
action = /usr/share/samba/panic-action %d</FONT></SPAN></DIV>
<DIV> </DIV><SPAN class=600214818-30042008><FONT face=Arial size=2>
<DIV><BR>####### Authentication #######</DIV>
<DIV> </DIV>
<DIV># "security = user" is always a good idea. This will require a Unix
account<BR># in this server for every user accessing the server. See<BR>#
/usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html<BR># in the
samba-doc package for details.<BR> security = user</DIV>
<DIV> </DIV>
<DIV># You may wish to use password encryption. See the section on<BR>#
'encrypt passwords' in the smb.conf(5) manpage before enabling.<BR>
encrypt passwords = true</DIV>
<DIV> </DIV>
<DIV># If you are using encrypted passwords, Samba will need to know what<BR>#
password database type you are using. <BR> passdb backend =
smbpasswd<BR> enable privileges = yes<BR> obey pam
restrictions = yes</DIV>
<DIV> </DIV>
<DIV>; guest account = nobody<BR>; invalid users =
root</DIV>
<DIV> </DIV>
<DIV>; username map = /etc/samba/smbusers</DIV>
<DIV> </DIV>
<DIV># This boolean parameter controls whether Samba attempts to sync the
Unix<BR># password with the SMB password when the encrypted SMB password in
the<BR># passdb is changed.<BR> unix password sync = yes</DIV>
<DIV> </DIV>
<DIV># For Unix password sync to work on a Debian GNU/Linux system, the
following<BR># parameters must be set (thanks to Ian Kahan <<<A
href="mailto:kahan@informatik.tu-muenchen.de">kahan@informatik.tu-muenchen.de</A>>
for<BR># sending the correct chat script for the passwd program in Debian
Sarge).<BR> passwd program = /usr/bin/passwd %u<BR>
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:*
%n\n *password\supdated\ssuccessfully* .</DIV>
<DIV> </DIV>
<DIV># This boolean controls whether PAM will be used for password changes<BR>#
when requested by an SMB client instead of the program listed in<BR># 'passwd
program'. The default is 'no'.<BR> pam password change = yes</DIV>
<DIV> </DIV>
<DIV>########## Domains ###########</DIV>
<DIV> </DIV>
<DIV># Is this machine able to authenticate users. Both PDC and BDC<BR># must
have this setting enabled. If you are the BDC you must<BR># change the 'domain
master' setting to no<BR>#<BR> domain logons = yes<BR>#<BR># The
following setting only takes effect if 'domain logons' is set<BR># It specifies
the location of the user's profile directory<BR># from the client point of
view)<BR># The following required a [profiles] share to be setup on the<BR>#
samba server (see below)<BR>; logon path = <A
href="file://\\%N\profiles\%U">\\%N\profiles\%U</A><BR># Another common choice
is storing the profile in the user's home directory<BR>; logon path
= <A href="file://\\%N\%U\profile">\\%N\%U\profile</A><BR># no roaming
profiles<BR> logon path =<BR> logon home = </DIV>
<DIV> </DIV>
<DIV><BR># The following setting only takes effect if 'domain logons' is
set<BR># It specifies the location of a user's home directory (from the
client<BR># point of view)<BR> logon drive = H:<BR>;
logon home = <A href="file://\\%N\%U">\\%N\%U</A></DIV>
<DIV> </DIV>
<DIV># The following setting only takes effect if 'domain logons' is set<BR># It
specifies the script to run during logon. The script must be stored<BR># in the
[netlogon] share<BR># NOTE: Must be store in 'DOS' file format
convention<BR> logon script = netlogon.bat</DIV>
<DIV> </DIV>
<DIV># This allows Unix users to be created on the domain controller via the
SAMR<BR># RPC pipe. The example command creates a user account with a
disabled Unix<BR># password; please adapt to your needs<BR>; add user script =
/usr/sbin/adduser --quiet --disabled-password --gecos "" %u<BR>add user script =
useradd -m -G staff %u</DIV>
<DIV> </DIV>
<DIV>########## Printing ##########</DIV>
<DIV> </DIV>
<DIV># If you want to automatically load your printer list rather<BR># than
setting them up individually then you'll need this<BR> load printers
= no</DIV>
<DIV> </DIV>
<DIV># lpr(ng) printing. You may wish to override the location of the<BR>#
printcap file<BR>; printing = bsd<BR>; printcap name =
/etc/printcap</DIV>
<DIV> </DIV>
<DIV># CUPS printing. See also the cupsaddsmb(8) manpage in the<BR>#
cupsys-client package.<BR>; printing = cups<BR>;
printcap name = cups</DIV>
<DIV> </DIV>
<DIV># When using [print$], root is implicitly a 'printer admin', but you
can<BR># also give this right to other users to add drivers and set printer<BR>#
properties<BR>; printer admin = @ntadmin</DIV>
<DIV> </DIV>
<DIV><BR>############ Misc ############</DIV>
<DIV> </DIV>
<DIV># Using the following line enables you to customise your configuration<BR>#
on a per machine basis. The %m gets replaced with the netbios name<BR># of the
machine that is connecting<BR>; include =
/home/samba/etc/smb.conf.%m</DIV>
<DIV> </DIV>
<DIV># Most people will find that this option gives better performance.<BR># See
smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html<BR>#
for details<BR># You may want to add the following on a Linux
system:<BR># SO_RCVBUF=8192
SO_SNDBUF=8192<BR> socket options = TCP_NODELAY</DIV>
<DIV> </DIV>
<DIV># The following parameter is useful only if you have the linpopup
package<BR># installed. The samba maintainer and the linpopup maintainer
are<BR># working to ease installation and configuration of linpopup and
samba.<BR>; message command = /bin/sh -c '/usr/bin/linpopup "%f"
"%m" %s; rm %s' &</DIV>
<DIV> </DIV>
<DIV># Domain Master specifies Samba to be the Domain Master Browser. If
this<BR># machine will be configured as a BDC (a secondary logon server),
you<BR># must set this to 'no'; otherwise, the default behavior is
recommended.<BR> domain master = yes<BR> preferred
master = yes<BR> local master = yes<BR># Some defaults for winbind
(make sure you're not using the ranges<BR># for something
else.)<BR>; idmap uid = 10000-20000<BR>; idmap gid =
10000-20000<BR>; template shell = /bin/bash<BR>;<BR>; The following
was the default behaviour in sarge<BR>; but samba upstream reverted the default
because it might induce<BR>; performance issues in large organizations<BR>; See
#368251 for some of the consequences of *not* having<BR>; this setting and
smb.conf(5) for all details<BR>;<BR> winbind enum groups =
yes<BR> winbind enum users = yes</DIV>
<DIV> </DIV>
<DIV>#======================= Share Definitions =======================</DIV>
<DIV> </DIV>
<DIV>[homes]<BR> comment = Home Directories<BR>
browseable = no</DIV>
<DIV> </DIV>
<DIV># By default, the home directories are exported read-only. Change next<BR>#
parameter to 'yes' if you want to be able to write to them.<BR>
writable = yes</DIV>
<DIV> </DIV>
<DIV># File creation mask is set to 0700 for security reasons. If you want
to<BR># create files with group=rw permissions, set next parameter to
0775.<BR> create mask = 0700</DIV>
<DIV> </DIV>
<DIV># Directory creation mask is set to 0700 for security reasons. If you want
to<BR># create dirs. with group=rw permissions, set next parameter to
0775.<BR> directory mask = 0700</DIV>
<DIV> </DIV>
<DIV># Restrict access to home directories <BR># to the one of the authenticated
user<BR># This might need tweaking when using external authentication
schemes<BR> valid users = %S</DIV>
<DIV> </DIV>
<DIV># Un-comment the following and create the netlogon directory for Domain
Logons<BR># (you need to configure Samba to act as a domain controller
too.)<BR>[netlogon]<BR> comment = Network Logon
Service<BR> path = /home/samba/netlogon<BR> guest ok =
yes<BR> writable = no<BR> share modes =
no<BR> browseable = no<BR> read only = yes</DIV>
<DIV> </DIV>
<DIV># Un-comment the following and create the profiles directory to store<BR>#
users profiles (see the "logon path" option above)<BR># (you need to configure
Samba to act as a domain controller too.)<BR># The path below should be writable
by all users so that their<BR># profile directory may be created the first time
they log on<BR>;[profiles]<BR>; comment = Users
profiles<BR>; path = /home/samba/profiles<BR>; guest ok
= no<BR>; browseable = no<BR>; create mask =
0600<BR>; directory mask = 0700</DIV>
<DIV> </DIV>
<DIV>;[printers]<BR>; comment = All Printers<BR>;
browseable = no<BR>; path = /var/spool/samba<BR>;
printable = yes<BR>; public = no<BR>; writable =
no<BR>; create mode = 0700</DIV>
<DIV> </DIV>
<DIV># Windows clients look for this share name as a source of downloadable<BR>#
printer drivers<BR>#[print$]<BR># comment = Printer
Drivers<BR># path = /home/samba/printers<BR># browseable
= yes<BR># read only = yes<BR># guest ok = no<BR>##
Uncomment to allow remote administration of Windows print drivers.<BR># Replace
'ntadmin' with the name of the group your admin users are<BR># members
of.<BR>; write list = root, @ntadmin</DIV>
<DIV> </DIV>
<DIV>[greenblue]<BR> comment = General GreenBlue
Information<BR> path = /home/samba/greenblue<BR>
browseable = yes<BR> read only = no<BR> writeable =
yes<BR> printable = no<BR> inherit permissions =
yes<BR> create mode = 0660<BR> valid users =
@staff<BR> force group = staff<BR> force create mode =
0660<BR> force directory mode = 0770</DIV>
<DIV> </DIV>
<DIV>[greenblue-x]<BR> comment = GreenBlue Business
Information<BR> path = /home/samba/greenblue-x<BR> read
only = no<BR> writeable = yes<BR> printable =
no<BR> inherit permissions = yes<BR> create mode =
0660<BR> force directory mode = 0770<BR> force group =
corporate<BR> valid users = @corporate</DIV>
<DIV> </DIV>
<DIV>[projects]<BR> comment = Project Information for
GreenBlue<BR> path = /home/samba/projects<BR> read only
= no<BR> writeable = yes<BR> printable =
no<BR> inherit permissions = yes<BR> create mode =
0660<BR> force directory mode = 0770<BR> force group =
staff<BR> valid users = @staff</DIV>
<DIV> </DIV>
<DIV>[training]<BR> comment = Training Resources<BR>
path = /home/samba/training<BR> read only = no<BR>
writeable = yes<BR> printable = no<BR> inherit
permissions = yes<BR> create mode = 0660<BR> force
directory mode = 0770<BR> force group = staff<BR> valid
users = @staff</DIV>
<DIV> </DIV>
<DIV>[netboot]<BR> comment = Boot Loader Files for the
Network<BR> path = /tftpboot<BR> read only = no<BR> writeable =
yes<BR> printable = no<BR> inherit permissions = yes<BR> create
mode = 0777<BR> force directory mode = 0777<BR> force group =
staff<BR> valid users = @staff<BR></FONT></SPAN></DIV></BODY></HTML>