samba - Jan 1999 - Problems running apps from Samba 2.0.0 share on NT 4.0

Ever since I upgraded from Samba 1.9.18 to 2.0.0, I've been
having problems with applications started from a Samba share dying
silently, or with an Illegal Instruction message, on NT 4.0
Workstation.  Since the only configuration change has been the Samba
upgrade, that would seem to be the orgin of the problem.  Below is my
smb.conf file, in case I have something configured (or not configured)
which might be causing it.  If you know of anything I can look for in
the samba log (and what log level to use to get it), I would
appreciate it.

# Samba config file created using SWAT
# from localhost (127.0.0.1)
# Date: 1999/01/21 23:55:35

# Global parameters
	workgroup = TIVOLI-NT
	server string = Sten Drescher's home SMB server
	security = SERVER
	encrypt passwords = Yes
	password server = austin2-nt arbor-nt haydn
	smb passwd file = /etc/smbpasswd
	username map = /etc/smb.username
	log level = 2
	log file = /var/log/samba-log.%m
	max log size = 50
	read bmpx = No
	socket options = TCP_NODELAY
	add user script = /usr/sbin/useradd %u
	local master = No
	wins server = 146.84.3.8
	lock dir = /var/lock/samba
	remote announce = 146.84.3.255/Tivoli-Support 146.84.110.255/Tivoli-Support
	create mask = 0644

[homes]
	comment = Home Directories
	read only = No
	create mask = 0750
	browseable = No

[printers]
	comment = All Printers
	path = /var/spool/samba
	create mask = 0700
	print ok = Yes
	browseable = No

[winapps]
	comment = Windows Applications
	path = /winapps
	read only = No
	volume = Windows Applications

[wingames]
	comment = Windows Games
	path = /wingames
	read only = No
	volume = Windows Games

[cdrom0]
	comment = KeyFontsPro for Windows and Macintosh
	path = /mnt/cdrom
	guest ok = Yes
	root preexec = /bin/mount /mnt/cdrom || /bin/mount /mnt/cdrom
	root postexec = /bin/umount /mnt/cdrom
	volume = CD-ROM 0

[cdrom1]
	comment = USENIX 1997 Annual Technical Conference and USELINUX
	path = /mnt/cdrom1
	guest ok = Yes
	root preexec = /bin/mount /mnt/cdrom1 || /bin/mount /mnt/cdrom1
	root postexec = /bin/umount /mnt/cdrom1
	volume = USENIX_Anaheim_97

[cdrom2]
	comment = 11th Systems Administration Conference
	path = /mnt/cdrom2
	guest ok = Yes
	root preexec = /bin/mount /mnt/cdrom2 || /bin/mount /mnt/cdrom2
	root postexec = /bin/umount /mnt/cdrom2
	volume = USENIX_LISA-97

[cdrom3]
	comment = 1998 USENIX Annual Technical Conference
	path = /mnt/cdrom3
	guest ok = Yes
	root preexec = /bin/mount /mnt/cdrom3 || /bin/mount /mnt/cdrom3
	root postexec = /bin/umount /mnt/cdrom3
	volume = USENIX_New_Orleans_98

[cdrom4]
	comment = 12th Systems Administration Conference
	path = /mnt/cdrom4
	guest ok = Yes
	root preexec = /bin/mount /mnt/cdrom4 || /bin/mount /mnt/cdrom4
	root postexec = /bin/umount /mnt/cdrom4
	volume = USENIX_LISA_98

[cdrom5]
	comment = Java Reference Library
	path = /mnt/cdrom5
	guest ok = Yes
	root preexec = /bin/mount /mnt/cdrom5 || /bin/mount /mnt/cdrom5
	root postexec = /bin/umount /mnt/cdrom5
	volume = JRL

[cdrom6]
	comment = PalmPilot: The Ultimate Guide
	path = /mnt/cdrom6
	guest ok = Yes
	root preexec = /bin/mount /mnt/cdrom6 || /bin/mount /mnt/cdrom6
	root postexec = /bin/umount /mnt/cdrom6
	volume = Ultimat_Pilot

[cdrom7]
	comment = CD-ROM 7
	path = /mnt/cdrom7
	guest ok = Yes
	root preexec = /bin/mount /mnt/cdrom7 || /bin/mount /mnt/cdrom7
	root postexec = /bin/umount /mnt/cdrom7
	available = No
	volume = CD-ROM 7


-- 
#include <disclaimer.h>                               /* Sten Drescher */
Unsolicited bulk email will be stored and handled for a US$500/KB fee.
Amendment II, Revised: A well-regulated population being necessary to
the security of a police state, the right of the Government to keep
and destroy arms shall not be infringed.

> Ever since I upgraded from Samba 1.9.18 to 2.0.0, I've been having
> problems with applications started from a Samba share dying silently,
> or with an Illegal Instruction message, on NT 4.0 Workstation.  
Sten,

I think you are experiencing the same problem I had when I upgraded to 
2.0.0 beta 5.

It seems that the smbd daemons are actually dying, which can produce 
anything from "Network Read" errors to full GPFs.

The way to check if your smbd processes are the culprit is to set up a 
cron job which appends the output of smbstatus to a file every 10 minutes.
Then when someone complains about errors, check that the 'pid' for that 
user didn't change.

I couldn't find anything obvious in the log, and a message to samba-bugs 
has got no reply yet.  Lack of time has meant that I have slipped back to 
the 1.9.* version we were using before.

HTH.


Cheers,

Duncan Kinnear,
McCarthy and Associates,			Email:  duncan@McCarthy.co.nz
PO Box 764, McLean Towers,			Phone:  +64 6 834 3360
Shakespeare Road, Napier, New Zealand.		Fax:    +64 6 834 3369
-------------------------------------------------------------------------------
Providing Integrated Software to the Meat Processing Industry for over 10 years