Subject: Re: Samba weirdness on -current?
To: Scott Ellis <firstname.lastname@example.org>
From: Laine Stump <email@example.com>
Date: 02/02/2000 04:10:13
At 09:07 PM 2/1/00 -0800, Scott Ellis wrote:
>I decided to update my kernel and libc from Dec 16th to Feb 01, and now
>Samba has stopped working. I rebuilt both 2.0.6 and 2.0.7pre1 (ya never
>know), both with the same results.
I don't know if this is realated, but about a week ago there were a few
messages about a bug in -current wrt Samba 2.0.6. See:
and other messages with the same subject in:
All of this doesn't bode well for me - Samba is one of the "very essential"
packages on my NetBSD box, and I've been wanting to upgrade from 2.0.3 to
something newer to see if it gets rid of all these problems I'm having with
files getting out of sync in MSVC++. But I can't upgrade to 2.0.6 according
to the previous emails, and now you're saying it's dangerous for me to
build a new kernel. Ouch!!
>What I see when running "smbd -d 10" and trying to look at a share is:
>[2000/02/01 20:49:25, 10] lib/genrand.c:do_reseed(135)
> do_reseed: got 40 bytes from /dev/urandom.
>[2000/02/01 20:49:25, 4] locking/shmem_sysv.c:sysv_shm_open(547)
> Trying sysv shmem open of size 65535
>(I set "shared mem size = 65535" in smb.conf, just in case the shared mem
>limit in the kernel was hosed, and was blocking the original 1M
>This repeats twice, and then the attempt to mount the share (or just browse
>it with smbclient) fails.
>Has anyone else seen this? I'm using the same smb.conf that I've been using
>for ages, so I don't think that's it, but...who knows. ;-)
> Scott Ellis