SAMBA 2.2.8 misc issues.

John E. Malmberg wb8tyw at qsl.net
Fri Aug 13 00:08:38 GMT 2004


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.

The one with the SAMBA 2.0.6 release on the OpenVMS Freeware 5.0 can be 
used as a start, and updated to the newer images.


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.

A command procedure to set this up is in the SAMBA 2.0.6 release as above.


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.

This is an inconsistent behavior, and indicates that something is not 
working where utility is trying to determine if it is running as root or 
not.


4. I strongly recommend not using the /VAXC qualifier in compiling.  All 
it is doing is suppressing error messages, and is intended for ease of 
compiling code in migration to ANSI compliance or legacy code that is 
not being maintained anymore.

The SAMBA UNIX code is ANSI compliant and does not need the /VAXC 
switch, and using on new code is just helping to hide any new bugs 
introduced.

Adding /ENABLE=WARN=(LEVEL4,QUESTCODE) turns on a LINT like feature in 
DECC, and while some of the messages are noise, many of the messages 
that it exposes are real bugs.

Fixes are in the UNIX SAMBA stream for bugs that were exposed with the 
above switch when building SAMBA on VMS.

The noise messages like unused include files, can be suppressed with 
#pragma messages in the config.h.

And example of that is in the config_vms.h file with the SAMBA 2.0.6 
release mentioned above.


Regards,
-John
wb8tyw at qsl.net
Personal Opinion Only



More information about the samba-vms mailing list