The configuration file installed during upgrade is an empty file. In /etc/samba : # ls -al drwxr-xr-x 3 root root 4096 Nov 10 12:29 . drwxr-xr-x 75 root root 4096 Nov 10 12:30 .. -rw-r--r-- 1 root root 0 Nov 10 12:29 ._cfg0000_smb.conf -rw-r--r-- 1 root root 7808 Nov 10 12:29 ._cfg0000_smb.conf.example.gz -rw-r--r-- 1 root root 204 Nov 10 12:29 ._cfg0000_smbusers [cut end of list] Very dangerous if etc-update is used to fast !!! It has been happening for the past 3 upgrades (most of them minor revisions). I realized it since 3.0.7. Re-emerging the package (no upgrade) does not produce the problem. Reproducible: Always Steps to Reproduce: 1. emerge -u samba (need to be a real upgrade) 2. 3. Actual Results: samba emerge correctly but /etc/samba/._cfg0000_smb.conf is an empty file. Expected Results: install an updated version of smb.conf as ._cfg0000_smb.conf root@saturn # emerge info Portage 2.0.51-r3 (gcc34-amd64-2004.1, gcc-3.4.2, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r1 x86_64) ================================================================= System uname: 2.6.9-gentoo-r1 x86_64 4 Gentoo Base System version 1.4.16 Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.90.0.1.1-r3 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache distlocks fixpackages" GENTOO_MIRRORS="ftp:///ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ ftp://gentoo.netnitco.net/pub/mirrors/gentoo/source/ ftp://mirror.pudas.net/gentoo http://gentoo.tiscali.nl/gentoo/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/disk0/gentoo/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /usr/local/bmg-main" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="X alsa amd64 apm avi berkdb bitmap-fonts cdr cups curl divx4linux doc dvd dvdr encode esd f77 fam fftw foomaticdb fortran gdbm gif gimp gimpprint gnome gnomedb gpm gstreamer gtk gtk2 gtkhtml imlib java jpeg kerberos ldap libg++ libwww lua mozilla mozsvg mpeg mysql ncurses nptl odbc oggvorbis opengl oss pam pdflib perl plotutils png postgres ppds python readline samba sdl slang spell ssl tcltk tcpd tiff truetype v4l v4l2 xml xml2 xmms xprint xv zlib"
In fact the latest problem I have is that there is a default smb.conf file that's preloaded with a bunch of settings. This file should really be called smb.conf.example and every emerge of a new Samba should NOT try to overwrite a users settings with the default package file. No other package behaves this way, they all install it to smb.conf.example. This occurs even in the latest Samba file.
ok 3.0.14a-r2 and will stop doing that. Now there will be *no* smb.conf installed at all, just the smb.conf.example.gz file (taking a page out of portage). Should it be ungzipped first though? dunno -- file a separate bug if you think so.
