Set gid problem hpux10.20 2.0.7-2 binary package

[Steve Cirivello]

First, without reservation, thanks for the solution.  I'm indirectly
involved with Samba at a production environment site and it meets the
need there wonderfully.  I'm now involved in the early learning curve to
roll out Samba at my first production site.

My bench test configuration is an HP 9000/800 G50 box, fresh install of
HP-UX 10.20, Y2K patch bundle, patch PHCO_20441 (for libc), download and
install 2.0.7-2 binary package.  There's a W98 machine and NT4
Workstation on the 3-node test network.

Here's my first simple smb.conf:
[global]
        workgroup = WORKGROUP
        encrypt passwords = yes
[firstsh]
        comment = First share
        path = /samba2072
        read only = yes
        guest ok = yes

Daemons start without error.  I can access my simple test share by
explictly mapping it, but I cannot browse.  If I do the network
neighborhood thing, or do a net view command, the following  messages
appear in log.smb about 5 times:

[2000/10/01 16:54:44, 0] lib/util_sec.c:(69)
  Failed to set gid privileges to (-1,-2) now set to (0,0) uid=(0,0)
[2000/10/01 16:54:44, 0] lib/util.c:(2381)
  PANIC: failed to set gid

I don't have the HP ANSI C compiler, so I used gzip, binutils (2.9.1),
gcc (2.95.2) and built the "latest" Samba from source using the same
options (except for compiler options) that were documented for the
binary package.  These executables yield the following messages in
log.smb about 5 times:

[2000/10/01 19:43:10, 0] lib/util_sec.c:assert_gid(72)
  Failed to set gid privileges to (-1,-2) now set to (0,0) uid=(0,0)
[2000/10/01 19:43:10, 0] lib/util.c:smb_panic(2381)
  PANIC: failed to set gid

The only other thing I came up with is a web search yielding something
about bug #51331 on Debian, but it appeared to be a kernel bug.

I'm going to try an earlier version of Samba (I have 2.0.5a on CD with
the O'Reilly book.)  However, after spending most of the day today
trying to solve this myself, I hope you folks don't mind this inquiry.

Here's the HP passwd and group files (there's something about user
nobody that I suspect is important.)

root:4ZmRQQQlxQdE:0:3::/:/sbin/sh
daemon:*:1:5::/:/sbin/sh
bin:*:2:2::/usr/bin:/sbin/sh
sys:*:3:3::/:
adm:*:4:4::/var/adm:/sbin/sh
uucp:*:5:3::/var/spool/uucppublic:/usr/lbin/uucp/uucico
lp:*:9:7::/var/spool/lp:/sbin/sh
nuucp:*:11:11::/var/spool/uucppublic:/usr/lbin/uucp/uucico
hpdb:*:27:1:ALLBASE:/:/sbin/sh
nobody:*:-2:-2::/:
stevec:NpkqQQQQFCgIc:101:20:,,,:/home/stevec:/usr/bin/sh

root::0:root
other::1:root,hpdb
bin::2:root,bin
sys::3:root,uucp
adm::4:root,adm
daemon::5:root,daemon
mail::6:root
lp::7:root,lp
tty::10:
nuucp::11:nuucp
users::20:root,stevec
nogroup:*:-2:

I did change the nobody user in the passwd file from -2:-24 to -2:-2 per
an HP support article, but it didn't fix the problem (the numbers in the
log file messages did match the nobody user settings though.)

Thanks for your time and assistance.

Steve Cirivello
Arcturus Computing
-------------- next part --------------
HTML attachment scrubbed and removed