SAMBA 2.2.8 misc issues.

[COLLOT Jean-Yves]

> 1. There does not appear to be a command procedure to add to the user's 
> login.com or SYLOGIN.COM to set up the foreign commands for SAMBA.

Yes, I am going to add an updated version of the Samba 2.0.6
SAMBA_COMMANDS.COM procedure in the next release.

> 2. The smb.conf is referencing an obsolete Pathworks guest account for 
> the guest account.  A dedicated account with it's own UIC is needed for 
> this.

Yes again. I'll include the MAKE_SAMBA_GUEST_ACCOUNT.COM from Samba 2.0.6 in
the next release. Note, however, that, for security reasons, I am not sure
it is such good idea to have a valid guest account.

> 3. There seems to be some issues when running utilities from an account 
> that has more than tmpmbx and netmbx, but less than all privileges.  It 
> causes diagnostics about SYSLCK being missing to be generated.

I thought that this problem was fixed since the 07-Aug-2003 version.
Apparently, I was wrong. 
I can't be sure, but I don't think that the problem lies with the method of
determining if the user is root or not. The SYSLCK privilege, as far as I
know (and as far as I wanted it to be) is only needed by SMBD.EXE and
NMBD.EXE
Anyway, I need more information about that : which utilities are concerned;
which specific command(s), if any; which additional privileges (more than
tmpmbx and netmbx) ?

> 4. I strongly recommend not using the /VAXC qualifier in compiling.  

There was already a couple of messages about that. 

I have not changed my mind: I don't agree with that recommendation, and with
the arguments you give to support it. I guess we've had different
experiences, and that yours and mine lead us toward different conclusions.

However, even if I think it's not useful, it cannot add problems to remove
that option, and I guess most of the Samba/VMS users will be happier without
it.
So, let's not mind about who is right (may be both of us, depending on
circumstances) : the SAMBA UNIX code is ANSI compliant (I'll add "almost",
if you don't mind), so it's not a such a huge work to remove that "awful"
/STANDARD=VAXC switch, and replace it by the /WARN=(ENABLE=LEVEL4,QUESTCODE)
you propose. Actually, the full option I am working on currently is
/WARN=(ENABLE=(LEVEL4,QUESTCODE),NOINFORMATIONALS), and it will be used in
the next release.

JY