I have exactly that .
nogroup:x:65534:root
but I do not see account nobody as part of the nogroup. I did download the
source and use rpm -bb with the spec file. It kept failing due to no make
file. I entered the ./configure command only to build the Makefile and
headers (i think). I then built an rpm using rpm -bb samba.spec. I then
removed the old samba packages using rpm -e and installed the new samba
packages that I created. I was patting myself on the back, maybe
prematurely. I am wondering if this is winbind not resolving "nobody" to
the NT PDC. I have not found much on this but am still working on it.
Thanks always.
Peter
"Post, Mark K" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
07/15/2002 01:53 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Upgrading Samba from 2.2.0a to 2.2.5
Peter,
Are you saying /etc/group does not have an entry in there that looks like
this:
nogroup:x:65534:root
??
I'm speculating that this is an example of why I and others keep repeating
that if you have a system managed by RPM, and you want to upgrade a
package
on it, that you really should use RPM to do it, and use the .spec file
from
the current version as a starting point. The Samba RPM distributed by
SuSE
had these commands in it (I've manually done some of the symbolic
substitution to make it a little more readable):
CONFIGURE_OPTS=" \
--prefix=/usr \
--libdir=/usr/lib/samba \
--localstatedir=/usr/var/lib/samba \
--mandir=/usr/share/man \
--sbindir=/usr/sbin \
--with-codepagedir=/usr/share/samba/codepages \
--with-privatedir=//usr/etc/samba \
--with-configdir=//usr/etc/samba \
--with-swatdir=/usr/share/samba/swat \
--with-sambabook=/usr/share/doc/packages/samba/htmldocs/using_samba
\
--with-logfilebase=/usr/var/log/samba \
--with-lockdir=/usr/var/lib/samba \
--with-automount \
--with-smbmount \
--with-smbwrapper \
--with-piddir=/usr/var/run/samba \
--with-pam \
--with-pam_smbpass \
--with-syslog \
--with-quotas \
--with-utmp \
--with-msdfs \
--with-vfs \
--with-libsmbclient \
--with-acl-support \
--with-winbind \
--with-sgml-share=/usr/share"
cd source
cp -f /usr/share/automake/config.sub ./config.sub
cp -f /usr/share/automake/config.guess ./config.guess
autoconf
CFLAGS=-O2 -Wall -O -D_GNU_SOURCE -D_LARGEFILE64_SOURCE ./configure
$CONFIGURE_OPTS
make PASSWD_PROGRAM=/usr/bin/passwd
make nsswitch
make nsswitch/libnss_wins.so
cd ../examples/VFS
autoconf
./configure $CONFIGURE_OPTS
make
export USE_KAVPSHAREDLIB=0
for module in fprot kaspersky mks openantivirus; do
make -C ${module}
done
I don't know if all those values specified are the defaults or not, but
since I really don't want to spend the time to find out, I used what SuSE
used rather than take all defaults.
Other commands followed these, but the point is that if you want a package
to properly replace the one you have, you need to configure it pretty much
the way the original was configured.
Mark Post
-----Original Message-----
From: Peter E. Abresch Jr. - at Pepco [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 15, 2002 12:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Upgrading Samba from 2.2.0a to 2.2.5
I used ./configure as is and took all defaults. In the smb.conf I do have
"guest account = nobody" just like I had in 2.2.0a smb.conf. In fact it is
the exact smb.conf.
I also have winbindd running. I configured the nsswitch.conf to reflect
the following:
passwd: files winbind
group: files winbind
In /etc/passwd I have
nobody:x:65534:65534:nobody:/var/lib/nobody:/bin/bash
nobody does belong to any group.
Thanks for any info.
Peter
"Post, Mark K" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
07/15/2002 09:55 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Upgrading Samba from 2.2.0a to 2.2.5
Peter,
What was the exact ./configure command you wound up issuing?
Also, what do you have specified in smb.conf for "guest account?" It
defaults to "nobody." What does the entry in /etc/passwd and /etc/groups
look like for that user?
Mark Post
-----Original Message-----
From: Peter E. Abresch Jr. - at Pepco [mailto:[EMAIL PROTECTED]]
Sent: Sunday, July 14, 2002 9:30 PM
To: [EMAIL PROTECTED]
Subject: Re: Upgrading Samba from 2.2.0a to 2.2.5
I ran into many problems upgrading from Samba 2.2.0a to 2.2.5. In the long
run, all these problems were mine, caused by lack of understanding of what
was going on. I was missing many SuSE Development packages at first that I
had to install. Then it took me a day to figure out that I had to run
./configure from the Samba source to build the Makefile and the proper
headers.
I feel confident that the next upgrade will go a lot smoother. I learn
from my mistakes so I learned a lot.
I am able to map drives and everything seems to work fine. However I see
the following messages in the log:
Jul 14 20:07:18 ibm9672 smbd[2944]: [2002/07/14 20:07:18, 0]
smbd/sec_ctx.c:initialise_groups(229)
Jul 14 20:07:18 ibm9672 smbd[2944]: Unable to initgroups. Error was
Operation not permitted
These ring a bell so I spent most of the day researching it. I pretty much
came up empty. I know it has something to do with account "nobody" but can
no longer find my notes. Do I need to worry about these messages? Is there
anyway to eliminate them?
Thanks to everyone that responded. Your assistance was much appreciated.
Peter
"Post, Mark K" <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
07/12/2002 12:09 PM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: Re: Upgrading Samba from 2.2.0a to 2.2.5
Peter,
I just executed the rpm rebuild on my SuSE 7.0 system, with the 2.2.16
kernel. It seemed to work fine for me. The error you report is generated
by the configure command in /usr/src/packages/BUILD/samba-2.2.5/source/.
You might take a look at the config.log file in that directory. The very
last thing that I have in mine is this:
configure:13522: checking for poptGetContext in -lpopt
configure:13541: gcc -o conftest -O -O2 -Wall -O -D_GNU_SOURCE
-D_LARGEFILE64_SOURCE conftest.c -lpopt -ldl -lnsl -lpam 1>&5
configure:13565: checking whether to use included popt
configure:13580: checking configure summary
configure:13589: gcc -o conftest -O -O2 -Wall -O -D_GNU_SOURCE
-D_LARGEFILE64_SOURCE conftest.c -ldl -lnsl -lpam -lpopt 1>&5
In file included from configure:13586:
tests/summary.c:4: warning: return-type defaults to `int'
Yours will probably have some sort of error with the compilation of the
summary check.
Mark Post
-----Original Message-----
From: Peter E. Abresch Jr. - at Pepco [mailto:[EMAIL PROTECTED]]
Sent: Friday, July 12, 2002 8:40 AM
To: [EMAIL PROTECTED]
Subject: Re: Upgrading Samba from 2.2.0a to 2.2.5
I tried the suggestion below because it looked the easiest. I get the
following when I do the 'rpm --rebuild samba-2.2.5-0.src.rpm
checking whether to use traditional smbpasswd file... yes
--More--configure: error: summary failure. Aborting config
Bad exit status from /var/tmp/rpm-tmp.98694 (%build)
checking whether to use NISPLUS_HOME... no
checking whether to use SSL... no
checking whether to use syslog logging... yes
When I do SMBD -V I still get Version 2.2.0a
I looked over samba.conf but being the newbie I am, I really do not see
anything that stands out. Does anyone have any ideas? Much appreciated.
Peter
<[EMAIL PROTECTED]>
07/11/2002 04:07 PM
To: "Peter E. Abresch Jr. - at Pepco" <[EMAIL PROTECTED]>
cc: <[EMAIL PROTECTED]>
Subject: Re: Upgrading Samba from 2.2.0a to 2.2.5
On Thu, 11 Jul 2002, Peter E. Abresch Jr. - at Pepco wrote:
> We are running SuSE SLES7 beta Linux Kernel 2.4.7. The Samba delivered
was
> Samba 2.2.0a. I used YAST to install the source and created a source
tree
> under /usr/src/samba-2.2.0a. I downloaded all the patches and
successfully
> applied them up to 2.2.5.
>
> My question is where do I go from here? I know I have to compile the
> source. What are the commands or sequence of commands necessary? I here
a
> lot about the .spec file. What is it and what do I do with it? Are there
> any gotchas? I appreciate any assistance this newbie can receive.
Thanks.
Another solution is to download the src rpm for samba 2.2.5 from :
ftp://ftp.suse.com/pub/people/lmuelle/src/
Depending on the options you need you will probably have to modify the
spec for the rpm to tune it to your needs. If not you can rebuild directly
from the src rpm using :
rpm --rebuild samba-2.2.5-0.src.rpm
If you have to change the spec file (it contains the configure command)
then first install the src rpm
rpm -i samba-2.2.5-0.src.rpm
Then modify the spec file, I think you will find it in
/usr/src/packages/SPEC
(don't forget the increase the Release field after each modification of
the spec file)
Then build the s390.rpm files using
rpm -bb samba.spec
Have fun with it,
Tim
--
===========================================================================
Tim Verhoeven
Linux & Open Source Specialist
GSM : 0496 / 693 453 + e-business solutions
Email : [EMAIL PROTECTED] + consulting
URL : www.sin.khk.be/~dj/ + Server consolidation
===========================================================================
