more samba4 upgrade problems: share not accessible

[Aaron Solochek]

I'm going to try to give a complete picture of my install here.  I built the
latest git source, configured with:

./configure --disable-rpath --disable-rpath-install --localstatedir=/var
--sysconfdir=/etc --prefix=/usr/local/samba --with-piddir=/var/run

That is basically the same configuration the debian packages I was previously
using used.  I'm doing this so if those packages ever get fixed, I can go back
to using them.

Then I created links in /usr/local/{bin,sbin,lib,share} for everything in
/usr/local/samba.  I made sure to create links for everything, including stuff
down in the python subdirectories.

I moved /usr/local/samba/private to private.orig and replaced it with a link to
/var/lib/samba/private, since that's where my data lives.

I am not sure if /usr/local/samba/modules needs to be linked to from somewhere else.


When I try to get to my share, windows says "an internal error has occurred."

I ran samba with log level = 4 and debug level = 6, and attached it.  The log is
nothing more than starting the server, double clicking on my windows share to
get the error message, then stopping the server.

I can't tell if the log even shows anything about the connection.  The share
name is bitbucket.  I see it parsing the config and disconnecting when I
shutdown the server, but that's it.  Hopefully someone else will see something
useful in the log.

-Aaron
-------------- next part --------------
A non-text attachment was scrubbed...
Name: samba.log.debug.bz2
Type: application/octet-stream
Size: 9096 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20110111/d1be16bd/attachment.obj>