Samba server setup

[Marty]

I'm trying to re-establish the setup that I had for Samba on my eCS
machine after my fresh installation (due to a hard drive failure) but
I'm missing one piece that I can't identify.

I have Security/2 installed properly with a root user set up and working
login. I had to do an ad-hoc "install" of Samba on the new eCS system
because I don't have the original installation files, but I do have the
previously installed image.

I created some directories in c:\mptn\etc\samba for it, but I have the
feeling I don't have everything there that I need. I have so far:

mptn\etc\samba\lock
mptn\etc\samba\pid
mptn\etc\samba\private

And I created an smbd.conf and placed it out there too. I was able to
start SMBD and have it run up until I created the "private" directory.
Then I used smbpasswd to create the root user and password corresponding
to Security/2. Now when I try to launch SMBD, it just exits immediately
without output on the console. When I run it with -d=99, I get the log
listed below. It seems to be complaining about printing, but I've done
my best to tell it that I had no interest in printing whatsoever in the
smbd.conf file. Any hints are appreciated. SMBD.conf file available on
request (although the non-commented parts that were parsed are listed in
this log).

LOG FILE FOLLOWS:
[2009/03/30 13:12:12, 1] lib/util_unistr.c:load_case_tables(63)
creating lame upcase table
[2009/03/30 13:12:12, 1] lib/util_unistr.c:load_case_tables(78)
creating lame lowcase table
[2009/03/30 13:12:12, 0] smbd/server.c:main(760)
smbd version 3.0.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2009/03/30 13:12:12, 0] smbd/server.c:main(794)
standard input is not a socket, assuming -D option
[2009/03/30 13:13:17, 5] lib/debug.c:debug_dump_status(367)
INFO: Current debug levels:
all: True/99
tdb: False/0
printdrivers: False/0
lanman: False/0
smb: False/0
rpc_parse: False/0
rpc_srv: False/0
rpc_cli: False/0
passdb: False/0
sam: False/0
auth: False/0
winbind: False/0
vfs: False/0
idmap: False/0
quota: False/0
acls: False/0
[2009/03/30 13:13:17, 1] lib/util_unistr.c:load_case_tables(63)
creating lame upcase table
[2009/03/30 13:13:17, 1] lib/util_unistr.c:load_case_tables(78)
creating lame lowcase table
[2009/03/30 13:13:17, 0] smbd/server.c:main(760)
smbd version 3.0.9 started.
Copyright Andrew Tridgell and the Samba Team 1992-2004
[2009/03/30 13:13:17, 2] smbd/server.c:main(764)
uid=0 gid=0 euid=0 egid=0
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
Build environment:
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
Built by: ***@WORK
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
Built on: Mon Jul 4 23:40:10 MSD 2005
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
Built using: gcc
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
Build host: OS/2 WORK 1 4.50 i386
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SRCDIR: .
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
BUILDDIR: .
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)

Paths:
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SBINDIR: /usr/local/samba/sbin
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
BINDIR: /usr/local/samba/bin
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SWATDIR: /usr/local/samba/swat
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
CONFIGFILE: C:\MPTN\ETC/samba/smb.conf
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
LOGFILEBASE: .
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
LMHOSTSFILE: C:\MPTN\ETC/samba/lmhosts
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
LIBDIR: /usr/local/samba/lib
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SHLIBEXT: so
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
LOCKDIR: C:\MPTN\ETC/samba/lock
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
PIDDIR: C:\MPTN\ETC/samba/pid
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SMB_PASSWD_FILE: C:\MPTN\ETC/samba/private/smbpasswd
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
PRIVATE_DIR: C:\MPTN\ETC/samba/private
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)

System Headers:
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_CDEFS_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_FCNTL_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_FILIO_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_IOCTL_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_IPC_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_MOUNT_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_PARAM_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_RESOURCE_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_SELECT_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_SOCKET_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_SOCKIO_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_STATFS_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_STATVFS_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_STAT_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_SYSLOG_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_TERMIO_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_TIME_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_TYPES_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_UNISTD_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_VFS_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYS_WAIT_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)

Headers:
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_ARPA_INET_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_CTYPE_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_DIRENT_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_FCNTL_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_GLOB_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_GRP_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_INTTYPES_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_LIMITS_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_LOCALE_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_MEMORY_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_NETINET_IN_SYSTM_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_NETINET_IP_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_NETINET_TCP_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_NET_IF_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_NSSWITCH_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_NSS_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STDARG_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STDINT_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STDLIB_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRINGS_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRING_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYSLOG_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_TERMIOS_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_TERMIO_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_UNISTD_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_UTIME_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)

UTMP Options:
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_UTMP_H
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_UT_UT_HOST
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_UT_UT_NAME
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_UT_UT_TIME
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
WITH_UTMP
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)

HAVE_* Defines:
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_ATEXIT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_C99_VSNPRINTF
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_CHMOD
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_COMPILER_WILL_OPTIMIZE_OUT_FNS
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_CONNECT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_DEVICE_MAJOR_FN
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_DEVICE_MINOR_FN
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_DUP2
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_ENDNETGRENT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_ERRNO_DECL
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_EXECL
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_EXPLICIT_LARGEFILE_SUPPORT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_FCNTL_LOCK
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_FGETXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_FLISTXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_FREMOVEXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_FSETXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_FSTAT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_FSYNC
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_FTRUNCATE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_FTRUNCATE_EXTEND
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_FUNCTION_MACRO
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_GETCWD
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_GETTIMEOFDAY_TZ
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_GETXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_GLOB
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_ICONV
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_IMMEDIATE_STRUCTURES
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_INITGROUPS
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_LGETXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_LIBSOCKET
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_LINK
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_LISTXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_LLISTXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_LONGLONG
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_LREMOVEXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_LSETXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_MAKEDEV
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_MEMMOVE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_MEMSET
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_MKNOD
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_MKTIME
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_NATIVE_ICONV
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_NO_ACLS
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_PASSWD_PW_AGE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_PASSWD_PW_COMMENT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_PATHCONF
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_PIPE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_RAND
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_RANDOM
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_READLINK
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_REALPATH
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_REMOVEXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_RENAME
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_ROOT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SELECT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SETBUFFER
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SETENV
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SETLOCALE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SETPGID
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SETSID
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SETXATTR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SIGACTION
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SIGPROCMASK
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SIG_ATOMIC_T_TYPE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SNPRINTF
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SNPRINTF_DECL
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SRAND
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SRANDOM
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STAT_ST_BLKSIZE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STAT_ST_BLOCKS
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRCASECMP
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRCHR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRDUP
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRERROR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRFTIME
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRLCAT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRLCPY
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRNDUP
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRNLEN
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRPBRK
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRTOUL
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_STRUCT_STAT_ST_RDEV
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_ST_RDEV
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYMLINK
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_SYSCONF
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_UNIXSOCKET
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_USLEEP
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_UTIMBUF
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_UTIME
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_UTIMES
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_VA_COPY
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_VOLATILE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_VSNPRINTF
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_VSNPRINTF_DECL
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE_WAITPID
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__CHDIR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__CLOSE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__CLOSEDIR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__DUP
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__DUP2
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__FCNTL
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__FORK
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__FSTAT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__GETCWD
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__LSEEK
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__LSTAT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__OPEN
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__OPENDIR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__READ
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__READDIR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__SEEKDIR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__STAT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__TELLDIR
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE__WRITE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE___CLOSE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE___DUP
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE___DUP2
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE___FCNTL
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE___FORK
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE___READ
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
HAVE___WRITE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)

--with Options:
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
WITH_UTMP
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)

Build Options:
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
BROKEN_NISPLUS_INCLUDE_FILES
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
COMPILER_SUPPORTS_LL
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
DEFAULT_DISPLAY_CHARSET
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
DEFAULT_DOS_CHARSET
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
DEFAULT_UNIX_CHARSET
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
PACKAGE_BUGREPORT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
PACKAGE_NAME
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
PACKAGE_STRING
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
PACKAGE_TARNAME
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
PACKAGE_VERSION
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
REALPATH_TAKES_NULL
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
RETSIGTYPE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SEEKDIR_RETURNS_VOID
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SIZEOF_INO_T
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SIZEOF_INT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SIZEOF_LONG
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SIZEOF_OFF_T
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SIZEOF_SHORT
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
STAT_STATVFS
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
STAT_ST_BLOCKSIZE
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
STDC_HEADERS
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
STRING_STATIC_MODULES
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
SYSCONF_SC_NGROUPS_MAX
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
TIME_WITH_SYS_TIME
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
USE_SETEUID
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
loff_t
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
offset_t
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
static_init_auth
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
static_init_charset
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
static_init_idmap
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
static_init_pdb
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
static_init_rpc
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
static_init_vfs
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)

Type sizes:
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
sizeof(char): 1
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
sizeof(int): 4
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
sizeof(long): 4
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
sizeof(uint8): 1
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
sizeof(uint16): 2
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
sizeof(uint32): 4
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
sizeof(short): 2
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
sizeof(void*): 4
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)

Builtin modules:
[2009/03/30 13:13:17, 4] smbd/build_options.c:output(44)
pdb_smbpasswd pdb_tdbsam pdb_guest rpc_lsa rpc_reg rpc_lsa_ds
rpc_wks rpc_net rpc_dfs rpc_srv rpc_spoolss rpc_samr idmap_tdb
auth_rhosts auth_sam auth_unix auth_winbind auth_server auth_domain
auth_builtin
[2009/03/30 13:13:17, 3] param/loadparm.c:lp_load(3911)
lp_load: refreshing parameters
[2009/03/30 13:13:17, 3] param/loadparm.c:init_globals(1318)
Initialising global parameters
[2009/03/30 13:13:17, 3] param/params.c:pm_process(566)
params.c:pm_process() - Processing configuration file
"C:\MPTN\ETC/samba/smb.conf"
[2009/03/30 13:13:17, 3] param/loadparm.c:do_section(3404)
Processing section "[global]"
doing parameter printing = sysv
doing parameter load printers = no
doing parameter guest account = nobody
doing parameter null passwords = yes
doing parameter log file = log.%m
doing parameter workgroup = MYGROUP
doing parameter ea support = yes
[2009/03/30 13:13:17, 2] param/loadparm.c:do_section(3421)
Processing section "[cdrive]"
[2009/03/30 13:13:17, 8] param/loadparm.c:add_a_service(2306)
add_a_service: Creating snum = 0 for cdrive
doing parameter comment = eCS Boot Drive
doing parameter path = c:/
doing parameter valid users = root
doing parameter browseable = yes
doing parameter public = no
doing parameter writable = yes
doing parameter printable = no
[2009/03/30 13:13:17, 4] param/loadparm.c:lp_load(3944)
pm_process() returned Yes
[2009/03/30 13:13:17, 7] param/loadparm.c:lp_servicenumber(4054)
lp_servicenumber: couldn't find homes
[2009/03/30 13:13:17, 8] param/loadparm.c:add_a_service(2306)
add_a_service: Creating snum = 1 for IPC$
[2009/03/30 13:13:17, 3] param/loadparm.c:lp_add_ipc(2388)
adding IPC service
[2009/03/30 13:13:17, 8] param/loadparm.c:add_a_service(2306)
add_a_service: Creating snum = 2 for ADMIN$
[2009/03/30 13:13:17, 3] param/loadparm.c:lp_add_ipc(2388)
adding IPC service
[2009/03/30 13:13:17, 10] param/loadparm.c:set_server_role(3851)
set_server_role: role = ROLE_STANDALONE
[2009/03/30 13:13:17, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(UTF-16LE,ASCII) 1 0
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(106)
Attempting to register new charset UCS-2LE
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(114)
Registered charset UCS-2LE
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(106)
Attempting to register new charset UTF-16LE
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(114)
Registered charset UTF-16LE
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(106)
Attempting to register new charset UCS-2BE
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(114)
Registered charset UCS-2BE
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(106)
Attempting to register new charset UTF-16BE
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(114)
Registered charset UTF-16BE
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(106)
Attempting to register new charset UTF8
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(114)
Registered charset UTF8
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(106)
Attempting to register new charset UTF-8
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(114)
Registered charset UTF-8
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(106)
Attempting to register new charset ASCII
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(114)
Registered charset ASCII
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(106)
Attempting to register new charset 646
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(114)
Registered charset 646
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(106)
Attempting to register new charset ISO-8859-1
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(114)
Registered charset ISO-8859-1
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(106)
Attempting to register new charset UCS2-HEX
[2009/03/30 13:13:17, 5] lib/iconv.c:smb_register_charset(114)
Registered charset UCS2-HEX
[2009/03/30 13:13:17, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(ASCII,UTF-16LE) 0 1
[2009/03/30 13:13:17, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(UTF-16LE,UTF-16LE) 1 1
[2009/03/30 13:13:17, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,UTF-16LE) 0 1
[2009/03/30 13:13:17, 8] lib/iconv.c:smb_iconv_open(257)
!!!!iconv_open(SYSTEM,UCS) = 17a87c
[2009/03/30 13:13:17, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,UTF-16LE) 0 1
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(257)
!!!!iconv_open(SYSTEM,UCS) = 17a87c
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,UTF-16LE) 0 1
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(257)
!!!!iconv_open(SYSTEM,UCS) = 17a87c
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(UTF8,UTF-16LE) 0 1
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(UTF-16LE,SYSTEM) 1 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(248)
!!!!iconv_open(UCS,SYSTEM) = 17a87c
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(UTF8,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(248)
!!!!iconv_open(UCS,SYSTEM) = 17a87c
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(UTF-16LE,SYSTEM) 1 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(248)
!!!!iconv_open(UCS,SYSTEM) = 17a87c
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(UTF8,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(248)
!!!!iconv_open(UCS,SYSTEM) = 17a87c
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(UTF-16LE,SYSTEM) 1 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(248)
!!!!iconv_open(UCS,SYSTEM) = 17a87c
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(UTF8,SYSTEM) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(248)
!!!!iconv_open(UCS,SYSTEM) = 17a87c
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(UTF-16LE,UTF8) 1 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,UTF8) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(257)
!!!!iconv_open(SYSTEM,UCS) = 17a87c
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,UTF8) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(257)
!!!!iconv_open(SYSTEM,UCS) = 17a87c
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(SYSTEM,UTF8) 0 0
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(257)
!!!!iconv_open(SYSTEM,UCS) = 17a87c
[2009/03/30 13:13:18, 8] lib/iconv.c:smb_iconv_open(211)
!!!!smb_iconv_open(UTF8,UTF8) 0 0
[2009/03/30 13:13:18, 2] lib/util_unistr.c:init_valid_table(177)
creating default valid table
[2009/03/30 13:13:18, 7] param/loadparm.c:lp_servicenumber(4054)
lp_servicenumber: couldn't find printers
[2009/03/30 13:13:18, 6] param/loadparm.c:lp_file_list_changed(2695)
lp_file_list_changed()
file C:\MPTN\ETC/samba/smb.conf -> C:\MPTN\ETC/samba/smb.conf last
mod_time: Mon Mar 30 13:12:04 2009

[2009/03/30 13:13:18, 2] lib/interface.c:add_interface(79)
added interface ip=192.168.7.198 bcast=192.168.7.255 nmask=255.255.255.0
[2009/03/30 13:13:18, 5] lib/util.c:init_names(260)
Netbios name list:-
my_netbios_names[0]="BENDER"
[2009/03/30 13:13:18, 3] smbd/server.c:main(790)
loaded services
[2009/03/30 13:13:18, 0] smbd/server.c:main(794)
standard input is not a socket, assuming -D option
[2009/03/30 13:13:18, 3] smbd/server.c:main(805)
Becoming a daemon.
[2009/03/30 13:13:18, 8] lib/util.c:fcntl_lock(1709)
fcntl_lock 6 8 0 1 3 = 0/3
[2009/03/30 13:13:18, 8] lib/util.c:fcntl_lock(1736)
fcntl_lock: Lock call successful
[2009/03/30 13:13:18, 2] lib/tallocmsg.c:register_msg_pool_usage(57)
Registered MSG_REQ_POOL_USAGE
[2009/03/30 13:13:18, 2] lib/dmallocmsg.c:register_dmalloc_msgs(71)
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
[2009/03/30 13:13:18, 5] lib/gencache.c:gencache_init(59)
Opening cache file at C:\MPTN\ETC/samba/lock/gencache.tdb
[2009/03/30 13:13:18, 5] libsmb/namecache.c:namecache_enable(58)
namecache_enable: enabling netbios namecache, timeout 660 seconds
[2009/03/30 13:13:18, 10] registry/reg_cachehook.c:reghook_cache_add(60)
reghook_cache_add: Adding key
[/HKLM/SYSTEM/CurrentControlSet/Control/Print]
[2009/03/30 13:13:18, 8] lib/adt_tree.c:sorted_tree_add(247)
sorted_tree_add: Enter
[2009/03/30 13:13:18, 11] lib/adt_tree.c:sorted_tree_find_child(232)
sorted_tree_find_child: Did not find [HKLM]
[2009/03/30 13:13:18, 11] lib/adt_tree.c:sorted_tree_birth_child(148)
sorted_tree_birth_child: First child of node [NULL]! [HKLM]
[2009/03/30 13:13:18, 11] lib/adt_tree.c:sorted_tree_find_child(232)
sorted_tree_find_child: Did not find [SYSTEM]
[2009/03/30 13:13:18, 11] lib/adt_tree.c:sorted_tree_birth_child(148)
sorted_tree_birth_child: First child of node [HKLM]! [SYSTEM]
[2009/03/30 13:13:18, 11] lib/adt_tree.c:sorted_tree_find_child(232)
sorted_tree_find_child: Did not find [CurrentControlSet]
[2009/03/30 13:13:18, 11] lib/adt_tree.c:sorted_tree_birth_child(148)
sorted_tree_birth_child: First child of node [SYSTEM]!
[CurrentControlSet]
[2009/03/30 13:13:18, 11] lib/adt_tree.c:sorted_tree_find_child(232)
sorted_tree_find_child: Did not find [Control]
[2009/03/30 13:13:18, 11] lib/adt_tree.c:sorted_tree_birth_child(148)
sorted_tree_birth_child: First child of node [CurrentControlSet]!
[Control]
[2009/03/30 13:13:18, 11] lib/adt_tree.c:sorted_tree_find_child(232)
sorted_tree_find_child: Did not find [Print]
[2009/03/30 13:13:18, 11] lib/adt_tree.c:sorted_tree_birth_child(148)
sorted_tree_birth_child: First child of node [Control]! [Print]
[2009/03/30 13:13:18, 10] lib/adt_tree.c:sorted_tree_add(314)
sorted_tree_add: Successfully added node
[HKLM/SYSTEM/CurrentControlSet/Control/Print] to tree
[2009/03/30 13:13:18, 8] lib/adt_tree.c:sorted_tree_add(316)
sorted_tree_add: Exit
[2009/03/30 13:13:18, 20] registry/reg_cachehook.c:reghook_dump_cache(109)
reghook_dump_cache: Starting cache dump now...
[2009/03/30 13:13:18, 20] lib/adt_tree.c:sorted_tree_print_children(340)
ROOT/: [HKLM] (NULL)
[2009/03/30 13:13:18, 20] lib/adt_tree.c:sorted_tree_print_children(340)
ROOT/HKLM/: [SYSTEM] (NULL)
[2009/03/30 13:13:18, 20] lib/adt_tree.c:sorted_tree_print_children(340)
ROOT/HKLM/SYSTEM/: [CurrentControlSet] (NULL)
[2009/03/30 13:13:18, 20] lib/adt_tree.c:sorted_tree_print_children(340)
ROOT/HKLM/SYSTEM/CurrentControlSet/: [Control] (NULL)
[2009/03/30 13:13:18, 20] lib/adt_tree.c:sorted_tree_print_children(340)
ROOT/HKLM/SYSTEM/CurrentControlSet/Control/: [Print] (data)
[2009/03/30 13:13:18, 10] printing/nt_printing.c:update_c_setprinter(447)
update_c_setprinter: c_setprinter = 0
[2009/03/30 13:13:18, 5] smbd/connection.c:claim_connection(170)
claiming 0
[2009/03/30 13:13:18, 3] printing/printing.c:start_background_queue(1224)
start_background_queue: Starting background LPQ thread
[2009/03/30 13:13:18, 5] printing/printing.c:start_background_queue(1228)
start_background_queue: background LPQ thread failed to start.
Invalid argument

[Paul Smedley]

Hi Marty,

Post by Marty
I'm trying to re-establish the setup that I had for Samba on my eCS
machine after my fresh installation (due to a hard drive failure) but
I'm missing one piece that I can't identify.

Make life easy for yourself :) Go to
http://members.aon.at/herwig.bauernfeind/samba/ and grab the current
warpin package - Herwig has made things pretty easy to setup :)

[Marty]

Post by Paul Smedley
Hi Marty,

Post by Marty
I'm trying to re-establish the setup that I had for Samba on my eCS
machine after my fresh installation (due to a hard drive failure) but
I'm missing one piece that I can't identify.

Make life easy for yourself :) Go to
http://members.aon.at/herwig.bauernfeind/samba/ and grab the current
warpin package - Herwig has made things pretty easy to setup :)

Hi Paul. Didn't want you to think I was ignoring you... ;-)

I haven't had a chance to give this a shot yet, but I certainly will.
Thanks for the response.

[Marty]

Post by Paul Smedley
Hi Marty,

Post by Marty
I'm trying to re-establish the setup that I had for Samba on my eCS
machine after my fresh installation (due to a hard drive failure) but
I'm missing one piece that I can't identify.

Make life easy for yourself :) Go to
http://members.aon.at/herwig.bauernfeind/samba/ and grab the current
warpin package - Herwig has made things pretty easy to setup :)

Went through the install and there were some errors. Firstly, I'm not
using XWP since the reinstall of my system, so creation of the ShareWiz
object was a problem. Then after that, it goes to run SSCC, which
proceeds to complain that it can't find "\SMB.CMD", "\TESTPARM.EXE", and
"\SMBPASSWD.EXE" (note the initial "\" which is no doubt causing the
problem). (When I run SSCC manually from the command line it seems to
work and doesn't make these complaints.)

After this, I go in and manually run SMB.CMD to start the server, and it
says that everything started successfully. But in reality, only NMBD
started successfully, and SMBD did exactly the same thing that it has
been doing all along. It starts up and craps out immediately. I need
to understand what SMBD.EXE is trying to do that's causing it to exit
immediately. Please note that it is not crashing, just gracefully and
uselessly exiting for no apparent reason.

So I'm afraid I need a little more help than those scripts and package
provide.

One thing I'd like to understand also... Is the Security/2 package a
requirement anymore? Can/should I uninstall it? How do I cleanly
remove my previous Samba installation and configuration to be sure that
it is not messing up anything?

[Paul Smedley]

Hi Marty,

Post by Marty

Post by Paul Smedley

Post by Marty
I'm trying to re-establish the setup that I had for Samba on my eCS
machine after my fresh installation (due to a hard drive failure) but
I'm missing one piece that I can't identify.

Make life easy for yourself :) Go to
http://members.aon.at/herwig.bauernfeind/samba/ and grab the current
warpin package - Herwig has made things pretty easy to setup :)

Went through the install and there were some errors. Firstly, I'm not
using XWP since the reinstall of my system, so creation of the ShareWiz
object was a problem. Then after that, it goes to run SSCC, which
proceeds to complain that it can't find "\SMB.CMD", "\TESTPARM.EXE", and
"\SMBPASSWD.EXE" (note the initial "\" which is no doubt causing the
problem). (When I run SSCC manually from the command line it seems to
work and doesn't make these complaints.)

I'll need to point Herwig to this thread so he can try and address
these problems.

Post by Marty
After this, I go in and manually run SMB.CMD to start the server, and it
says that everything started successfully. But in reality, only NMBD
started successfully, and SMBD did exactly the same thing that it has
been doing all along. It starts up and craps out immediately. I need
to understand what SMBD.EXE is trying to do that's causing it to exit
immediately. Please note that it is not crashing, just gracefully and
uselessly exiting for no apparent reason.
So I'm afraid I need a little more help than those scripts and package
provide.
One thing I'd like to understand also... Is the Security/2 package a
requirement anymore? Can/should I uninstall it? How do I cleanly
remove my previous Samba installation and configuration to be sure that
it is not messing up anything?

No - none of the builds currently available from
http://svn.netlabs.org/samba require Security/2 - however, it
shouldn't interfere with anything.

What happens if you try and start smbd as follows:
smbd -d 7 -l smbd.log

Anything obvious in the resulting log file? Feel free to mail me the
log for analysis if you like.

[Herwig Bauernfeind]

Hello Marty,

Post by Marty

Post by Paul Smedley

Post by Marty
I'm trying to re-establish the setup that I had for Samba on my eCS
machine after my fresh installation (due to a hard drive failure) but
I'm missing one piece that I can't identify.

Make life easy for yourself :) Go to
http://members.aon.at/herwig.bauernfeind/samba/ and grab the current
warpin package - Herwig has made things pretty easy to setup :)

Went through the install and there were some errors. Firstly, I'm not
using XWP since the reinstall of my system, so creation of the ShareWiz
object was a problem. Then after that, it goes to run SSCC, which
proceeds to complain that it can't find "\SMB.CMD", "\TESTPARM.EXE", and
"\SMBPASSWD.EXE" (note the initial "\" which is no doubt causing the
problem).

The "\" is not causing the problem - it is the result of the problem. :-)

Be sure you really got the latest WarpIN package, one of the earlier
revisions had a regression, where the installer would not change into
the installation directory and therefore could not find the stuff it
just installed. That sounds like your problem...

Security/2 is not used by Samba anymore, but it does not hurt if it is
installed.

Post by Marty
(When I run SSCC manually from the command line it seems to
work and doesn't make these complaints.)

Depending on the age of the WarpIN package you might try to run sscc.exe
/install to get going. But it would be definitely better to remove the
mess and start from scratch.

Post by Marty
After this, I go in and manually run SMB.CMD to start the server, and it
says that everything started successfully. But in reality, only NMBD
started successfully, and SMBD did exactly the same thing that it has
been doing all along. It starts up and craps out immediately. I need
to understand what SMBD.EXE is trying to do that's causing it to exit
immediately. Please note that it is not crashing, just gracefully and
uselessly exiting for no apparent reason.

Most likely it is complaining, that the guest account is missing and
that it cannot continue for that reason (you can see that in the last
lines of the logfile).

Post by Marty
One thing I'd like to understand also... Is the Security/2 package a
requirement anymore? Can/should I uninstall it? How do I cleanly
remove my previous Samba installation and configuration to be sure that
it is not messing up anything?

Uninstalling the WPI alone will not help you, as the WPI is designed not
to touch configuration files upon uninstall.

In order to really get rid of everything, do the following:

1.) Stop all Samba daemons.
2.) Uninstall Samba using Warpin.
3.) Run the following batch script:

--------------<killsamba.cmd>--------------
@echo off
del %UNIXROOT%\etc\master.passwd*
del %UNIXROOT%\etc\group*
del %UNIXROOT%\etc\*pwd*
echo Delete configuration stuff (most notably the .tdb files)
xdel %ETC%\samba\* /S /D /R /N
--------------<killsamba.cmd>--------------

xdel can be found here
http://hobbes.nmsu.edu/download/pub/os2/util/disk/xdel109.zip

4.) Last not least delete smbusers.ini, sscc.ini, smbmon.ini from the
former Samba installation directory.

5.) Start all over using the latest WPI.

Kind regards,
Herwig

[Marty]

Post by Herwig Bauernfeind
Hello Marty,

Post by Marty

Post by Paul Smedley

Post by Marty
I'm trying to re-establish the setup that I had for Samba on my eCS
machine after my fresh installation (due to a hard drive failure)
but I'm missing one piece that I can't identify.

Make life easy for yourself :) Go to
http://members.aon.at/herwig.bauernfeind/samba/ and grab the current
warpin package - Herwig has made things pretty easy to setup :)

Went through the install and there were some errors. Firstly, I'm not
using XWP since the reinstall of my system, so creation of the
ShareWiz object was a problem. Then after that, it goes to run SSCC,
which proceeds to complain that it can't find "\SMB.CMD",
"\TESTPARM.EXE", and "\SMBPASSWD.EXE" (note the initial "\" which is
no doubt causing the problem).

The "\" is not causing the problem - it is the result of the problem. :-)
Be sure you really got the latest WarpIN package, one of the earlier
revisions had a regression, where the installer would not change into
the installation directory and therefore could not find the stuff it
just installed. That sounds like your problem...

What is the latest? I (re-)grabbed 1.0.0.4 RC2 and (re-)tried it. Same
results on everything. I even tried letting it install to the default
location this time and it didn't help.

Post by Herwig Bauernfeind
Security/2 is not used by Samba anymore, but it does not hurt if it is
installed.

Nevertheless, I'll ditch it since Samba was the only reason I had it on
there to begin with.

Post by Herwig Bauernfeind

Post by Marty
(When I run SSCC manually from the command line it seems to work and
doesn't make these complaints.)

Depending on the age of the WarpIN package you might try to run sscc.exe
/install to get going. But it would be definitely better to remove the
mess and start from scratch.

Tried it both ways. SMBD still won't start. NMBD does, but SMBD always
exits "immediately".

Post by Herwig Bauernfeind

Post by Marty
After this, I go in and manually run SMB.CMD to start the server, and
it says that everything started successfully. But in reality, only
NMBD started successfully, and SMBD did exactly the same thing that it
has been doing all along. It starts up and craps out immediately. I
need to understand what SMBD.EXE is trying to do that's causing it to
exit immediately. Please note that it is not crashing, just
gracefully and uselessly exiting for no apparent reason.

Most likely it is complaining, that the guest account is missing and
that it cannot continue for that reason (you can see that in the last
lines of the logfile).

The only reference I see to this is that it is assigned to "nobody", but
I actually created a user called "nobody" and made this the guest
account. My previous Samba installation was like this and it was working.

Post by Herwig Bauernfeind

Post by Marty
One thing I'd like to understand also... Is the Security/2 package a
requirement anymore? Can/should I uninstall it? How do I cleanly
remove my previous Samba installation and configuration to be sure
that it is not messing up anything?

Uninstalling the WPI alone will not help you, as the WPI is designed not
to touch configuration files upon uninstall.
1.) Stop all Samba daemons.
2.) Uninstall Samba using Warpin.
--------------<killsamba.cmd>--------------
@echo off
del %UNIXROOT%\etc\master.passwd*
del %UNIXROOT%\etc\group*
del %UNIXROOT%\etc\*pwd*
echo Delete configuration stuff (most notably the .tdb files)
xdel %ETC%\samba\* /S /D /R /N
--------------<killsamba.cmd>--------------
xdel can be found here
http://hobbes.nmsu.edu/download/pub/os2/util/disk/xdel109.zip

(I've got a DELTREE here.) ;-)

Post by Herwig Bauernfeind
4.) Last not least delete smbusers.ini, sscc.ini, smbmon.ini from the
former Samba installation directory.
5.) Start all over using the latest WPI.

Tried it after cleaning it out twice now and I still see the same
problems. :-( Thanks for the info, though. I'll keep hacking at it.

[Herwig Bauernfeind]

Post by Marty

Post by Herwig Bauernfeind

Post by Marty

Post by Paul Smedley

Post by Marty
I'm trying to re-establish the setup that I had for Samba on my eCS
machine after my fresh installation (due to a hard drive failure)
but I'm missing one piece that I can't identify.

Make life easy for yourself :) Go to
http://members.aon.at/herwig.bauernfeind/samba/ and grab the current
warpin package - Herwig has made things pretty easy to setup :)

Went through the install and there were some errors. Firstly, I'm
not using XWP since the reinstall of my system, so creation of the
ShareWiz object was a problem. Then after that, it goes to run SSCC,
which proceeds to complain that it can't find "\SMB.CMD",
"\TESTPARM.EXE", and "\SMBPASSWD.EXE" (note the initial "\" which is
no doubt causing the problem).

The "\" is not causing the problem - it is the result of the problem. :-)
Be sure you really got the latest WarpIN package, one of the earlier
revisions had a regression, where the installer would not change into
the installation directory and therefore could not find the stuff it
just installed. That sounds like your problem...

What is the latest? I (re-)grabbed 1.0.0.4 RC2 and (re-)tried it. Same
results on everything. I even tried letting it install to the default
location this time and it didn't help.

1.0.0.4 RC2 is fine. It does not have that problem.

As I am working on RC3 at the moment, I'd be interested to find out what
's the reason for the problem you see and eventually fix it.

Post by Marty

Post by Herwig Bauernfeind
Security/2 is not used by Samba anymore, but it does not hurt if it is
installed.

Nevertheless, I'll ditch it since Samba was the only reason I had it on
there to begin with.

Post by Herwig Bauernfeind

Post by Marty
(When I run SSCC manually from the command line it seems to work and
doesn't make these complaints.)

Depending on the age of the WarpIN package you might try to run
sscc.exe /install to get going. But it would be definitely better to
remove the mess and start from scratch.

Tried it both ways. SMBD still won't start. NMBD does, but SMBD always
exits "immediately".

Post by Herwig Bauernfeind

Post by Marty
After this, I go in and manually run SMB.CMD to start the server, and
it says that everything started successfully. But in reality, only
NMBD started successfully, and SMBD did exactly the same thing that
it has been doing all along. It starts up and craps out
immediately. I need to understand what SMBD.EXE is trying to do
that's causing it to exit immediately. Please note that it is not
crashing, just gracefully and uselessly exiting for no apparent reason.

Most likely it is complaining, that the guest account is missing and
that it cannot continue for that reason (you can see that in the last
lines of the logfile).

The only reference I see to this is that it is assigned to "nobody", but
I actually created a user called "nobody" and made this the guest
account. My previous Samba installation was like this and it was working.

The installer and sscc.exe create and setup a guest account called
"guest" - this is hardcoded in several places at the moment (by
convention and cannot be changed easily at the moment). Needless to say,
a proper setup with a guest account called "nobody" will also work: It's
just not what the installer does at the moment.

My recommendation would be to let the installer create the guest account
as "guest" at first, then make sure everything works properly and later
change the guest account into "nobody".

It is very likely that parts of your Samba think the guest account is
"guest" and other parts think it is "nobody" in your case. Set the
loglevel to 5 and try to start smbd.exe, then check the log. The last
lines before smbd.exe exits will probably be something like "could not
setup guest account, exiting" or something like this.

Post by Marty

Post by Herwig Bauernfeind

Post by Marty
One thing I'd like to understand also... Is the Security/2 package a
requirement anymore? Can/should I uninstall it? How do I cleanly
remove my previous Samba installation and configuration to be sure
that it is not messing up anything?

Uninstalling the WPI alone will not help you, as the WPI is designed
not to touch configuration files upon uninstall.
1.) Stop all Samba daemons.
2.) Uninstall Samba using Warpin.
--------------<killsamba.cmd>--------------
@echo off
del %UNIXROOT%\etc\master.passwd*
del %UNIXROOT%\etc\group*
del %UNIXROOT%\etc\*pwd*
echo Delete configuration stuff (most notably the .tdb files)
xdel %ETC%\samba\* /S /D /R /N
--------------<killsamba.cmd>--------------
xdel can be found here
http://hobbes.nmsu.edu/download/pub/os2/util/disk/xdel109.zip

(I've got a DELTREE here.) ;-)

That will probably be fine, too ;-)

Post by Marty

Post by Herwig Bauernfeind
4.) Last not least delete smbusers.ini, sscc.ini, smbmon.ini from the
former Samba installation directory.
5.) Start all over using the latest WPI.

Tried it after cleaning it out twice now and I still see the same
problems. :-( Thanks for the info, though. I'll keep hacking at it.

Regards,
herwig

[Marty]

...

Post by Herwig Bauernfeind

Post by Marty
What is the latest? I (re-)grabbed 1.0.0.4 RC2 and (re-)tried it.
Same results on everything. I even tried letting it install to the
default location this time and it didn't help.

1.0.0.4 RC2 is fine. It does not have that problem.
As I am working on RC3 at the moment, I'd be interested to find out what
's the reason for the problem you see and eventually fix it.

Definitely not as straightforward as it seems. Firstly, I'm using
WarpIn 1.0.18.

Looking at the script, I see it's trying to execute "CMD" "/C
$(1)\coreinst.cmd ...". But this same "$(1)" is used to set up the
object paths above for SSCC and the XWP "Share this folder" object. It
works for SSCC (the object work directory and path are correct).

BUT! Remember, I don't have XWP installed right now. When it tried to
create the XWP_CONFIG object, I get a correct and informative error
message. Then everything after that point fails to resolve what $(1)
means. Maybe this is a WarpIn issue for Paul? In general, the package
shouldn't just assume that XWP is installed, or if it does, it should
have that as a prerequisite. But I think it might have clobbered the
path substitution in WarpIn after the error.

Post by Herwig Bauernfeind

Post by Marty

Post by Herwig Bauernfeind

Post by Marty
(When I run SSCC manually from the command line it seems to work and
doesn't make these complaints.)

Depending on the age of the WarpIN package you might try to run
sscc.exe /install to get going. But it would be definitely better to
remove the mess and start from scratch.

Tried it both ways. SMBD still won't start. NMBD does, but SMBD
always exits "immediately".

Post by Herwig Bauernfeind

Post by Marty
After this, I go in and manually run SMB.CMD to start the server,
and it says that everything started successfully. But in reality,
only NMBD started successfully, and SMBD did exactly the same thing
that it has been doing all along. It starts up and craps out
immediately. I need to understand what SMBD.EXE is trying to do
that's causing it to exit immediately. Please note that it is not
crashing, just gracefully and uselessly exiting for no apparent reason.

Most likely it is complaining, that the guest account is missing and
that it cannot continue for that reason (you can see that in the last
lines of the logfile).

The only reference I see to this is that it is assigned to "nobody",
but I actually created a user called "nobody" and made this the guest
account. My previous Samba installation was like this and it was working.

The installer and sscc.exe create and setup a guest account called
"guest" - this is hardcoded in several places at the moment (by
convention and cannot be changed easily at the moment). Needless to say,
a proper setup with a guest account called "nobody" will also work: It's
just not what the installer does at the moment.

Not a problem. I don't mind this setup for now. I did see the guest
user get created in the database as well as root.

Post by Herwig Bauernfeind
My recommendation would be to let the installer create the guest account
as "guest" at first, then make sure everything works properly and later
change the guest account into "nobody".
It is very likely that parts of your Samba think the guest account is
"guest" and other parts think it is "nobody" in your case. Set the
loglevel to 5 and try to start smbd.exe, then check the log. The last
lines before smbd.exe exits will probably be something like "could not
setup guest account, exiting" or something like this.

I'd love to let the installer do whatever it wants. But its selective
inability to find its own scripts is really throwing a monkey wrench
into the situation.

[Marty]

Post by Marty
I'd love to let the installer do whatever it wants. But its selective
inability to find its own scripts is really throwing a monkey wrench
into the situation.

This time, I cleaned everything out again, extracted all of the files
manually from the WPI, and then ran each step of the script manually.
Everything came up great! SSCC, SMBMon, everything!

While I have your ear, I saw one cosmetic problem with SSCC. When I
removed a share, it asked me if I was sure that I wanted to remove "%1"
instead of the share name. Also I couldn't figure out how to change the
name of the shares. I could modify the name of the objects by
Alt-Left-Clicking them and typing the new name, but this did not save to
the SMB.conf file. I went into the file manually to edit the share names.

So I'm not sure what happened inside of WarpIn, but it looks like the
package and scripts themselves are doing the right thing. I think it
has something to do with the unexpected failure to create the
XWP-related object.

I'd be glad to help debug this further if someone tells me what to do.

[Ilya Zakharevich]

Post by Marty

Post by Marty
I'd love to let the installer do whatever it wants. But its selective
inability to find its own scripts is really throwing a monkey wrench
into the situation.

This time, I cleaned everything out again, extracted all of the files
manually from the WPI, and then ran each step of the script manually.
Everything came up great! SSCC, SMBMon, everything!

Great! Is it documented how to make it manually? WarpIn, in my
experience, is such a PITA that I would always prefer manual configuration...

Thanks,
Ilya

[Herwig Bauernfeind]

Post by Ilya Zakharevich

Post by Marty

Post by Marty
I'd love to let the installer do whatever it wants. But its selective
inability to find its own scripts is really throwing a monkey wrench
into the situation.

This time, I cleaned everything out again, extracted all of the files
manually from the WPI, and then ran each step of the script manually.
Everything came up great! SSCC, SMBMon, everything!

Great! Is it documented how to make it manually? WarpIn, in my
experience, is such a PITA that I would always prefer manual configuration...

Look at http://svn.netlabs.org/samba

Specifically at http://svn.netlabs.org/samba/wiki/Cookbook

Now that's a PITA.

While it is certainly possible to install Samba manually, the WPI raised
the number of successful installations considerably, go figure...

Regards,
Herwig

[Ilya Zakharevich]

Post by Herwig Bauernfeind
Look at http://svn.netlabs.org/samba
Specifically at http://svn.netlabs.org/samba/wiki/Cookbook
Now that's a PITA.
While it is certainly possible to install Samba manually, the WPI raised
the number of successful installations considerably, go figure...

When WarpIn works, it may be very helpful (at least in some
situations). In my experience, it works less than in half of the
cases - and then the manual application is the only choice...

Ilya

[Paul Ratcliffe]

Post by Ilya Zakharevich

Post by Herwig Bauernfeind
Look at http://svn.netlabs.org/samba
Specifically at http://svn.netlabs.org/samba/wiki/Cookbook
Now that's a PITA.
While it is certainly possible to install Samba manually, the WPI raised
the number of successful installations considerably, go figure...

When WarpIn works, it may be very helpful (at least in some
situations). In my experience, it works less than in half of the
cases - and then the manual application is the only choice...

You are the most obtuse person I've ever come across.
Of course you never say specifically which packages you have problems with,
nor what those problems are, nor whether they are package specific or
related to WarpIN itself.
You just seem to like bashing things for the sake of it rather than
providing any constructive feedback.

[Marty]

Post by Ilya Zakharevich

Post by Marty

Post by Marty
I'd love to let the installer do whatever it wants. But its selective
inability to find its own scripts is really throwing a monkey wrench
into the situation.

This time, I cleaned everything out again, extracted all of the files
manually from the WPI, and then ran each step of the script manually.
Everything came up great! SSCC, SMBMon, everything!

Great! Is it documented how to make it manually? WarpIn, in my
experience, is such a PITA that I would always prefer manual configuration...

The CMD scripts in the WPI package are really handy and work well on my
system (when they get the chance to actually run). ;-)

I just extracted the WPI script and all the files in all packages (using
the -X and -x options). Then I went line-by-line for what the script
said. The script makes use of the other CMD files in the archive which
automate the annoying tasks very well.

Going to the next lower level involves the smb*.exe executables, which
I've done in the past with the older version, but it wasn't pretty.

[Paul Ratcliffe]

Post by Ilya Zakharevich
Great! Is it documented how to make it manually? WarpIn, in my
experience, is such a PITA that I would always prefer manual configuration...

<yawn>
Do you ever have anything constructive to say about anything?
Why don't you just STFU if not, eh?

[Herwig Bauernfeind]

Post by Marty

Post by Marty
I'd love to let the installer do whatever it wants. But its selective
inability to find its own scripts is really throwing a monkey wrench
into the situation.

Definitely! And believe me, I'll try to find out why and fix it if
possible. Unfortunately none of my three test machines show this behavior...

Post by Marty
This time, I cleaned everything out again,

Next WPI will have an option to clean out everything when uninstalling
the WPI. That already works here.

Post by Marty
extracted all of the files
manually from the WPI, and then ran each step of the script manually.
Everything came up great! SSCC, SMBMon, everything!
While I have your ear, I saw one cosmetic problem with SSCC. When I
removed a share, it asked me if I was sure that I wanted to remove "%1"
instead of the share name.

Hmm, that must be regression, will look into it. That used to work.

Post by Marty
Also I couldn't figure out how to change the
name of the shares. I could modify the name of the objects by
Alt-Left-Clicking them and typing the new name, but this did not save to
the SMB.conf file. I went into the file manually to edit the share names.

ACK. That's a missing feature. Noted down.

Post by Marty
So I'm not sure what happened inside of WarpIn, but it looks like the
package and scripts themselves are doing the right thing. I think it
has something to do with the unexpected failure to create the
XWP-related object.

I need to test that, I have XWP or eWP on all my test machines...

Post by Marty
I'd be glad to help debug this further if someone tells me what to do.

It might help me, if you enable "Debug" in SSCC.EXE, close it and
restart it and send me the output of the console window.

Your feedback is absolutely appreciated!

Kind regards,
Herwig

[Paul Ratcliffe]

Post by Marty
So I'm not sure what happened inside of WarpIn, but it looks like the
package and scripts themselves are doing the right thing. I think it
has something to do with the unexpected failure to create the
XWP-related object.
I'd be glad to help debug this further if someone tells me what to do.

Posting the relevant lines from WarpIN's install.log would be a good start.

[Marty]

Post by Paul Ratcliffe

Post by Marty
So I'm not sure what happened inside of WarpIn, but it looks like the
package and scripts themselves are doing the right thing. I think it
has something to do with the unexpected failure to create the
XWP-related object.
I'd be glad to help debug this further if someone tells me what to do.

Posting the relevant lines from WarpIN's install.log would be a good start.

I've sent it to your personal e-mail (I think!) and Herwig's. If you
don't get it, or need any more information, let me know. Thanks! (and
sorry for the LONG delay)

[Paul Ratcliffe]

Post by Marty

Post by Paul Ratcliffe

Post by Marty
So I'm not sure what happened inside of WarpIn, but it looks like the
package and scripts themselves are doing the right thing. I think it
has something to do with the unexpected failure to create the
XWP-related object.
I'd be glad to help debug this further if someone tells me what to do.

Posting the relevant lines from WarpIN's install.log would be a good start.

I've sent it to your personal e-mail (I think!) and Herwig's. If you
don't get it, or need any more information, let me know. Thanks! (and
sorry for the LONG delay)

The package is just a bit brain dead, that's all. Nothing wrong with WarpIN,
as I suspected.

[Herwig Bauernfeind]

Post by Paul Ratcliffe

Post by Marty

Post by Paul Ratcliffe

Post by Marty
So I'm not sure what happened inside of WarpIn, but it looks like the
package and scripts themselves are doing the right thing. I think it
has something to do with the unexpected failure to create the
XWP-related object.
I'd be glad to help debug this further if someone tells me what to do.

Posting the relevant lines from WarpIN's install.log would be a good start.

I've sent it to your personal e-mail (I think!) and Herwig's. If you
don't get it, or need any more information, let me know. Thanks! (and
sorry for the LONG delay)

The package is just a bit brain dead, that's all.

I realized that, too when looking at the logfile :-)

Besides the several superfluos cmd /c, which I will remove ASAP, I'd
appreciate any hint to enhance the package.

Post by Paul Ratcliffe
Nothing wrong with WarpIN, as I suspected.

That was my impression, too.

Kind regards,
Herwig

[Herwig Bauernfeind]

Post by Marty
...

Post by Herwig Bauernfeind

Post by Marty
What is the latest? I (re-)grabbed 1.0.0.4 RC2 and (re-)tried it.
Same results on everything. I even tried letting it install to the
default location this time and it didn't help.

1.0.0.4 RC2 is fine. It does not have that problem.
As I am working on RC3 at the moment, I'd be interested to find out
what 's the reason for the problem you see and eventually fix it.

Definitely not as straightforward as it seems. Firstly, I'm using
WarpIn 1.0.18.
Looking at the script, I see it's trying to execute "CMD" "/C
$(1)\coreinst.cmd ...". But this same "$(1)" is used to set up the
object paths above for SSCC and the XWP "Share this folder" object. It
works for SSCC (the object work directory and path are correct).

$(1) holds the directory where the binaries, scripts etc. are installed
into.

Post by Marty
BUT! Remember, I don't have XWP installed right now. When it tried to
create the XWP_CONFIG object, I get a correct and informative error
message. Then everything after that point fails to resolve what $(1)
means.

Ok, I need to verify this.

Post by Marty
Maybe this is a WarpIn issue for Paul?

Might be, but I need to do some research before making such a claim :-)
Paul R., if read this, a comment from your side would be appreciated.

Post by Marty
In general, the package shouldn't just assume that XWP is installed,
or if it does, it should have that as a prerequisite.

The Sharewiz is the only component that relies on XWP/eWP. It works
however also with WPSWizzard, which implements a similar feature. Must
think about that.

Post by Marty
But I think it might have clobbered the path substitution in WarpIn after the error.

We'll see.

Kind regards,
Herwig

[Paul Ratcliffe]

Post by Herwig Bauernfeind

Post by Marty
Looking at the script, I see it's trying to execute "CMD" "/C
$(1)\coreinst.cmd ...". But this same "$(1)" is used to set up the
object paths above for SSCC and the XWP "Share this folder" object. It
works for SSCC (the object work directory and path are correct).

$(1) holds the directory where the binaries, scripts etc. are installed
into.

Post by Marty
BUT! Remember, I don't have XWP installed right now. When it tried to
create the XWP_CONFIG object, I get a correct and informative error
message. Then everything after that point fails to resolve what $(1)
means.

Ok, I need to verify this.

Post by Marty
Maybe this is a WarpIn issue for Paul?

Might be, but I need to do some research before making such a claim :-)
Paul R., if read this, a comment from your side would be appreciated.

Not entirely sure what you want me to comment on...

Posting the package location would be a good start.

[Herwig Bauernfeind]

Post by Paul Ratcliffe

Post by Herwig Bauernfeind

Post by Marty
Looking at the script, I see it's trying to execute "CMD" "/C
$(1)\coreinst.cmd ...". But this same "$(1)" is used to set up the
object paths above for SSCC and the XWP "Share this folder" object. It
works for SSCC (the object work directory and path are correct).

$(1) holds the directory where the binaries, scripts etc. are installed
into.

Post by Marty
BUT! Remember, I don't have XWP installed right now. When it tried to
create the XWP_CONFIG object, I get a correct and informative error
message. Then everything after that point fails to resolve what $(1)
means.

Ok, I need to verify this.

Post by Marty
Maybe this is a WarpIn issue for Paul?

Might be, but I need to do some research before making such a claim :-)
Paul R., if read this, a comment from your side would be appreciated.

Not entirely sure what you want me to comment on...

.. if it is a possible at all, that the $(1) resolution fails, in case
an object cannot be created. However I did test specifically for that
case and $(1) resolution does _not_ fail (here) after an object could
not be created. So I don't think this is a WarpIN issue.

Post by Paul Ratcliffe
Posting the package location would be a good start.

http://msplins06.bon.at/%7Eadmin139/files/samba-1-0-0-4-rc3.wpi

PS: After reading your other message regarding install.log (which I did
not know before), I know there are at least several superfluos CMD.EXE
/C statements in my package...

Kind regards,
Herwig

[Paul Ratcliffe]

On Mon, 13 Apr 2009 06:12:46 +0200, Herwig Bauernfeind

Post by Herwig Bauernfeind

Post by Paul Ratcliffe

Post by Herwig Bauernfeind

Post by Marty
Looking at the script, I see it's trying to execute "CMD" "/C
$(1)\coreinst.cmd ...". But this same "$(1)" is used to set up the
object paths above for SSCC and the XWP "Share this folder" object. It
works for SSCC (the object work directory and path are correct).

$(1) holds the directory where the binaries, scripts etc. are installed
into.

Post by Marty
BUT! Remember, I don't have XWP installed right now. When it tried to
create the XWP_CONFIG object, I get a correct and informative error
message. Then everything after that point fails to resolve what $(1)
means.

Ok, I need to verify this.

Post by Marty
Maybe this is a WarpIn issue for Paul?

Might be, but I need to do some research before making such a claim :-)
Paul R., if read this, a comment from your side would be appreciated.

Not entirely sure what you want me to comment on...

.. if it is a possible at all, that the $(1) resolution fails, in case
an object cannot be created. However I did test specifically for that
case and $(1) resolution does _not_ fail (here) after an object could
not be created. So I don't think this is a WarpIN issue.

You are trying to create an object in the <XWP_CONFIG> folder. I don't
know why you are doing that, but you shouldn't be.
This is obviously doomed to failure if XWP is not installed.
There is nothing wrong with WarpIN's path resolution.

[Herwig Bauernfeind]

Post by Paul Ratcliffe
On Mon, 13 Apr 2009 06:12:46 +0200, Herwig Bauernfeind

Post by Herwig Bauernfeind

Post by Paul Ratcliffe

Post by Herwig Bauernfeind

Post by Marty
Looking at the script, I see it's trying to execute "CMD" "/C
$(1)\coreinst.cmd ...". But this same "$(1)" is used to set up the
object paths above for SSCC and the XWP "Share this folder" object. It
works for SSCC (the object work directory and path are correct).

$(1) holds the directory where the binaries, scripts etc. are installed
into.

Post by Marty
BUT! Remember, I don't have XWP installed right now. When it tried to
create the XWP_CONFIG object, I get a correct and informative error
message. Then everything after that point fails to resolve what $(1)
means.

Ok, I need to verify this.

Post by Marty
Maybe this is a WarpIn issue for Paul?

Might be, but I need to do some research before making such a claim :-)
Paul R., if read this, a comment from your side would be appreciated.

Not entirely sure what you want me to comment on...

.. if it is a possible at all, that the $(1) resolution fails, in case
an object cannot be created. However I did test specifically for that
case and $(1) resolution does _not_ fail (here) after an object could
not be created. So I don't think this is a WarpIN issue.

You are trying to create an object in the <XWP_CONFIG> folder. I don't
know why you are doing that, but you shouldn't be.

Because ShareWiz.exe is designed to be run from a folder's context menu.

It works either from XWP_CONFIG with eWP/XWP or the equivalent menu
configuration folder of WPS-Wizard.

Creating the object in the Samba folder does not make sense, as it will
not work from there.

Post by Paul Ratcliffe
This is obviously doomed to failure if XWP is not installed.

ACK, I should check whether that folder exists, before trying to create
an object in it.


Kind regards,
Herwig

[Herwig Bauernfeind]

Post by Herwig Bauernfeind

Post by Marty
...

Post by Herwig Bauernfeind

Post by Marty
What is the latest? I (re-)grabbed 1.0.0.4 RC2 and (re-)tried it.
Same results on everything. I even tried letting it install to the
default location this time and it didn't help.

1.0.0.4 RC2 is fine. It does not have that problem.
As I am working on RC3 at the moment, I'd be interested to find out
what 's the reason for the problem you see and eventually fix it.

Definitely not as straightforward as it seems. Firstly, I'm using
WarpIn 1.0.18.
Looking at the script, I see it's trying to execute "CMD" "/C
$(1)\coreinst.cmd ...". But this same "$(1)" is used to set up the
object paths above for SSCC and the XWP "Share this folder" object.
It works for SSCC (the object work directory and path are correct).

$(1) holds the directory where the binaries, scripts etc. are installed
into.

Post by Marty
BUT! Remember, I don't have XWP installed right now. When it tried
to create the XWP_CONFIG object, I get a correct and informative error
message. Then everything after that point fails to resolve what $(1)
means.

Ok, I need to verify this.

Post by Marty
Maybe this is a WarpIn issue for Paul?

Might be, but I need to do some research before making such a claim :-)
Paul R., if read this, a comment from your side would be appreciated.

Post by Marty
In general, the package shouldn't just assume that XWP is installed,
or if it does, it should have that as a prerequisite.

The Sharewiz is the only component that relies on XWP/eWP. It works
however also with WPSWizzard, which implements a similar feature. Must
think about that.

Post by Marty
But I think it might have clobbered the path substitution in WarpIn after the error.

We'll see.

I cannot reproduce this. Even if the ShareWiz object cannot be created,
subsequent path resolutions work normally here and installation
continues normally...

Regards,
Herwig

[Paul Ratcliffe]

Post by Marty
BUT! Remember, I don't have XWP installed right now. When it tried to
create the XWP_CONFIG object, I get a correct and informative error
message.

What is this thing that can't be created unless XWP is installed?

Post by Marty
Then everything after that point fails to resolve what $(1)
means. Maybe this is a WarpIn issue for Paul? In general, the package
shouldn't just assume that XWP is installed, or if it does, it should
have that as a prerequisite. But I think it might have clobbered the
path substitution in WarpIn after the error.

I've no idea. It seems very unlikely to me. What does WarpIN's install.log
say? Can anyone come up with a simple testcase?

[Marty]

Post by Paul Ratcliffe

Post by Marty
BUT! Remember, I don't have XWP installed right now. When it tried to
create the XWP_CONFIG object, I get a correct and informative error
message.

What is this thing that can't be created unless XWP is installed?

Post by Marty
Then everything after that point fails to resolve what $(1)
means. Maybe this is a WarpIn issue for Paul? In general, the package
shouldn't just assume that XWP is installed, or if it does, it should
have that as a prerequisite. But I think it might have clobbered the
path substitution in WarpIn after the error.

I've no idea. It seems very unlikely to me. What does WarpIN's install.log
say? Can anyone come up with a simple testcase?

Sorry for my slow response now. I haven't had the chance to get this
info yet. I will as soon as I can. Should I just e-mail you when I've
got it so you don't have to keep monitoring this thread? (Is your
reply-to close to correct?) :-)

[Herwig Bauernfeind]

Post by Marty

Post by Paul Ratcliffe

Post by Marty
BUT! Remember, I don't have XWP installed right now. When it tried
to create the XWP_CONFIG object, I get a correct and informative
error message.

What is this thing that can't be created unless XWP is installed?

Post by Marty
Then everything after that point fails to resolve what $(1) means.
Maybe this is a WarpIn issue for Paul? In general, the package
shouldn't just assume that XWP is installed, or if it does, it should
have that as a prerequisite. But I think it might have clobbered the
path substitution in WarpIn after the error.

I've no idea. It seems very unlikely to me. What does WarpIN's install.log
say? Can anyone come up with a simple testcase?

Sorry for my slow response now. I haven't had the chance to get this
info yet. I will as soon as I can. Should I just e-mail you when I've
got it so you don't have to keep monitoring this thread? (Is your
reply-to close to correct?) :-)

In case you don't post it here, please also drop me a note. Thx.

Herwig

[Herwig Bauernfeind]

Hello Marty,

did some research on your problem and found out at least one thing:

At the moment it is absolutely not recommended to call guest account
"nobody" instead of "guest". The main reason being
http://svn.netlabs.org/samba/ticket/59 and the necessity to add code to
workaround this in several places:

1.) It is hardcoded in sscc.exe in several places.
2.) It is hardcoded in smbusers.exe in one place.
3.) Usermod.CMD does not support it, even adding it later won't work.

So conclusion is:

Creating and using a guest account named "nobody" will trigger Ticket 59
immediately with todays set of tools.

If you insist on a guest account "nobody" at moment, forget about using
usermod.exe, sscc.exe and smbusers.exe and groups in general. Make sure
you understood what exactly happens in Ticket 59, and good luck when
working around it manually!

The next release of usermod.cmd will also support "nobody" as a guest
account and I might add support in smbusers.exe, too. This would allow
to use "nobody" as an alternative guest account name later (but not
during installation).

I will definitely not change sscc.exe and the installer, so out of the
box support for "nobody" will not be available until Ticket 59 is fixed
(which wont happen anytime soon).

Anyway, you seem to have another problem, too, because all that I said
does not explain why the installer seems to be unable to find the place
where it just installed stuff.... this still puzzles me.

Kind regards,
Herwig

[Marty]

Post by Herwig Bauernfeind
The next release of usermod.cmd will also support "nobody" as a guest
account and I might add support in smbusers.exe, too. This would allow
to use "nobody" as an alternative guest account name later (but not
during installation)

Is it smart to allow "nobody" to work as a guest account? Usually the
"nobody" account is used for things like servers that shouldn't have
access to terminals etc and it seems like a potential security leak to
have a normal "guest" that equals "nobody"
Dave

My "nobody" acts as a jail with no login shell. It doesn't have any
special access and can't get a shell. It's used primarily for updatedb,
which only browses (some) directories and can't write to them.

I'm not too attached to using this, but in general I don't want ANY
guest access to my Samba shares, so I would eventually like to disable
this to the degree possible.

[Herwig Bauernfeind]

Post by Herwig Bauernfeind
The next release of usermod.cmd will also support "nobody" as a guest
account and I might add support in smbusers.exe, too. This would allow
to use "nobody" as an alternative guest account name later (but not
during installation)

Is it smart to allow "nobody" to work as a guest account? Usually the
"nobody" account is used for things like servers that shouldn't have
access to terminals etc and it seems like a potential security leak to
have a normal "guest" that equals "nobody"

Well, I implemented that yesterday.

It is possible now to do the following:

1.) Install using "guest" as guest account.
2.) Create new guest account for "nobody", set Samba's guest account to
"nobody", remove original "guest" guest account.

It won't get better than that until someone fixes Ticket 59.

The updated binaries are not yet available from my page.
Stay tuned, they will be made available these days!

Kind regards,
Herwig