Donna Garverick wrote:

> i'm trying to get samba running on my 7.0 system....and (of
> course...because it's friday afternoon) am not having any
> luck.
>
> i'm seeing the following in log.smb (note the location!):
>
> /SAMBA/PUB/var: tail log.smb
> [2002/10/11 15:01:52, 1] lib/system.c:sys_chroot(420)
> WARNING: no chroot!
> [2002/10/11 15:01:52, 0]
> lib/util_sock.c:open_socket_in(904)  setsockopt:
> SO_REUSEADDR=0 on port 0 failed with error = Operation not
> supported on socket
> [2002/10/11 15:11:54, 0]
> lib/util_sock.c:set_socket_options(157)  Failed to set
> socket option TCP_NODELAY (Error Operation not supported on
> socket)
> [2002/10/11 15:11:54, 1] lib/system.c:sys_chroot(420)
> WARNING: no chroot!
> [2002/10/11 15:11:54, 0]
> lib/util_sock.c:open_socket_in(904)  setsockopt:
> SO_REUSEADDR=0 on port 0 failed with error = Operation not
> supported on socket


I believe that for Samba 2.0.7 these are all warnings that can be ignored.

You will see fewer warnings with the 2.2.5 that am I working on.


> what i've done
> 1) altacct samba/altuser mgr.samba to add pm
> 2) changed my versions of smbmon and nmbmon to run
> ?mb207.samba.sys (the critical run lines are identical to
> the hp-supplied jobs)
> 3) checked inetd.conf -- nmbp and smbp are commented out
> 4) checked services -- got entries for nmbp and smbp (on the
> default/standard port #s)
> 5) stop/started both listeners a lot of times
> 6) required files in /SAMBA/SMB207/lib are sane
> 7) /usr/local/samba points to /SAMBA/SMB207


Looks like you've done everything right.


> from network neighborhood, when i double-click on the icon
> for this system, i get asked for a password immediately --
> that's not normal.  i have one drive mapped on my pc to this
> box.  when i try to connect, i'm repeatedly asked for the
> password.  (yes, the registry fix is on my pc and i can
> easily connect to another mpe samba-enabled system)
>
> i'm out of guesses.....anyone got some new ones?        - d

Something that nearly drove me insane while testing 2.2.5 was somehow losing
the !EOJ statement in the JSMB job stream file.  The lack of an !EOJ was
causing fork() to fail, so new connections weren't being answered at the SMB
protocol level.  Just to make it interesting, *nothing* was showing up in the
log files.

So make sure your Samba job streams have !EOJ at the end.

If that's not the problem, try turning up "debug level =" in smb.conf to
increasingly higher levels until the log files contain helpful information.
--
[log in to unmask]
Remainder of .sig suppressed to conserve expensive California electrons...

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *