On 02/26/2012 07:56 AM, Michael Wood wrote:
Hi Steve
On 26 February 2012 02:20, steve<[email protected]> wrote:
On 02/25/2012 11:02 PM, Michael Wood wrote:
Hi
On 25 February 2012 04:26, steve<[email protected]> wrote:
Hi everyone
samba --version
Version 4.0.0alpha19-GIT-c9ef087
[...]
I found that the build had placed hundreds of links in the first
directory
in my path, /home/steve/bin. I moved the folder out of he path and the
commands began working again.
Hi Michael
Thanks for clearing this up. I got the update from git pull against the
previously checked out version. It is in /home/steve/samba-master and
/home/steve/bin is the first directory set in my path. mv-ing the bin folder
gave me the binaries under /usr/local/samba as I had had from previous
builds. It seems to be OK as the version numbers and dates under samba/bin
and sbin coincide with the date on which I built the source. I didn't
realise that the build used a temporary folder. Previous builds never put
anything in bin. Or maybe they did but deleted it afterwards. Anyway, I've
not lost anything in the process.
The build should never have put anything in /home/steve/bin, even
temporarily. It uses /home/steve/samba-master/bin while building. I
am not sure how you could have ended up with the stuff in
/home/steve/bin. There have been no significant changes to the build
system recently as far as I can see.
I've just written some scripts for posix-ifying s4 domain users and groups.
Only bash I'm afraid, no python. So I still don't think I'm qualified enough
for samba-technical;-)
You don't have to have written anything at all to join samba-technical :)
Joining might help you see what issues other people have with samba4
and how they are solved, or the occasional announcement about samba4
etc.
OK
I'm convinced. I'll take the plunge sometime today and hang around there
for a while. But fear not, I shall never post:-)
Steve
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
