; The SAMBA-VMS Frequently Asked Questions List - 01-Nov-2000    Index        Introduction  ,     General questions about SAMBA on OpenVMS       Printing Issues        Miscellaneous        Future directions      Changes since last edition  2     None, this is the first edition I am aware of.    C This is the Frequently Asked Questions (FAQ) posting for SAMBA-VMS.   A It contains answers to frequently asked questions about SAMBA for > OpenVMS on the SAMBA-VMS mailing list, and a few other places.    ? Other internet FAQs are generally available in these locations:   0         comp.answers and news.answers newsgroups)         ftp://rtfm.mit.edu/pub/usenet/...     0 This FAQ is archived in the following locations:    > Please do NOT send technical questions to the Frequently Asked@ Questions (FAQ) editor - well, please do not email any questionsC that do not also include the answer(s). Please post these questions @ to the appropriate SAMBA-VMS mailing list instead and see INTRO5? before posting. To make suggestions for changes or additions to D this FAQ list, please send mail to the FAQ editor at wb8tyw@qsl.net.  > Again, Please do not assume FAQ editor is not in a position to answer general questions.      Some general notes:   @ World-Wide Web Universal Resource Locator (URL) notation is used for FTP addresses.  6 Many people have contributed to this list, directly or6 indirectly. Many people have contributed to this list,0 directly or indirectly. In some cases, an answer; has been adapted from one or more postings on the SAMBA-VMS ; mailing list or comp.os.vms. Our thanks to all of those who 8 post answers. The name (or names) at the end of an entry8 indicate that the information was taken from postings by> those individuals; the text may have been edited for this FAQ.? These citations are only given to acknowledge the contribution.   > This contents of this FAQ are not to be considered an official; position of any companies whose employees have contributed.   @ These answers are provided in the hope that they will be of use,( but there are no guarantees of accuracy.  = Please also note that the current compiler of this FAQ is not 0 using any of the official versions of SAMBA-VMS.    1 All trademarks mentioned belong to their holders. ; DECUS, Pathworks, VMS and OpenVMS are trademarks of Compaq. = Microsoft Windows, and Microsoft Windows NT are trademarks of 
 Microsoft.( UNIX is a trademark of "The Open Group".     INTRO1.    What is SAMBA?  ?     SAMBA is an open source suite of programs for communicating ;     over the Microsoft NETBIOS protocols on TCP/IP.  It was ?     developed originally by Andrew Tridgell who is still active !     in guiding SAMBA's evolution.   >     For more information about SAMBA, see HTTP://WWW.SAMBA.ORG  @     Licensing for SAMBA is covered under the GNU Public License.  ,     The SAMBA-VMS home page is currently at:8     http://www.ifn.ing.tu-bs.de/ifn/sonst/samba-vms.html  <     It is maintained by Eckart Meyer, who is responsible for'     the majority of the SAMBA-VMS port.   :     With out the hard work of Eckart Meyer, there probably"     would not be a SAMBA-VMS port.       INTRO2.    What is VMS or OpenVMS?   ?     OpenVMS is an Computer Operating System sold by Compaq that A     is considered by many to be a superior operating environment.   A     The OpenVMS operating system has a reputation for reliability B     and security.  System uptimes can be measured in years.  It is3     also well known as an cracker resistant system.   :     A no-charge Hobby license for OpenVMS is available for     non-commercial home use.  F     For more information on OpenVMS, see http://www.openvms.compaq.com  B     For more information on the Free Hobby license for OpenVMS see%     http://www.montagar.com/Hobbyist/        INTRO3.   0 What is the scope of the SAMBA-VMS mailing list?  <     The samba-vms mailing list is the primary news group for&     OpenVMS specific issues for SAMBA.       INTRO4.   8 What other resources have SAMBA-VMS related information?  9     SAMBA for OpenVMS questions may show up in any of the 6     OpenVMS forums, Usually the comp.os.vms newsgroup.  7     DECUSERVE is a useful moderated forum that covers a 7     variety of computer related systems including SAMBA 4     for VMS.  It is run by volunteers from the DECUS     organization.   1     For information about DECUS and DECUSERVE see      http://www.decus.org       INTRO5.   1 How do I subscribe to the SAMBA-VMS mailing list?   ?     Before answering that, you should be aware of guidelines on      posting.  >     1. Please choose a subject title that accurately describes        your posting.  >     2. Please list the version of OpenVMS, SAMBA, and the name<        and version of the TCP/IP product that you are using./        Also mention any ECO or patches applied.   ?     3. Mailing lists are generally plain text only.  No HTML or A        Rich Text formats please.  Also please turn off VCF cards. >        Does it have to be mentioned that graphics as signature        files are also bad?  =     4. Please try to avoid attachments.  If you must place an >        attachment, if it can be read using a text editor, make=        sure that the name of the extension is .TXT to prevent )        problems with some virus scanners.   A     Also before posting, it is generally a good practice to check >     the archives of the mailing list and the FAQ to see if the'     question has been answered already.   <     [The following is likely to change in the future, as the;      SAMBA team at the time of this writing is reorganizing       it's mailing lists]  >     See INTRO6 for information about accessing the archives of     the SAMBA-VMS mailing list.   9     To subscribe to a list e-mail listproc@samba.org with 6     "subscribe listname Your Full Name" in the messageA     body. For additional information see http://lists.samba.org/.        INTRO6.   ; How do I access the archives of the SAMBA-VMS mailing list?   =     That is a good question.  Right now the old SAMBA mailing ;     lists are offline at the old server.  The SAMBA team is &     presently setting up a new server.  9     The old method involved going to http://www.samba.org <     then selecting a mirror site.  After which selecting the<     link to "archives" would give you a page where you could%     access the mailing list archives.   >     For now, some of the mailing list archives can be found at&     http://samba.cadcamlabs.org/lists/     INTRO7.   ? What versions of OpenVMS and TCPIP programs will SAMBA-VMS work  with?   <     OpenVMS versions from 5.5-2 and later are known to work.8     For VMS versions before 5.5-2 some versions of SAMBA:     require the AACRTL060 kit, which is a component of the     DEC C compiler.   9     SAMBA-VMS will work with any of the commercial TCP-IP (     programs that support UCX emulation.  9     The Compaq TCP/IP products are known as either UCX or 7     TCPIP Services for OpenVMS.  For non-commercial use :     they are available under the OpenVMS hobbyist program.  9     The Process Software company has MultiNet and TCPware 2     products available for commercial and are also1     available under the OpenVMS hobbyist program.   8     There is an experimental port of SAMBA-VMS using the2     OpenCMU-IP TCP/IP program that can be found at8     ftp://ftp.qsl.net/pub/wb8tyw/ .  It is not supported5     and there are no plans to enhance it further.  If 3     you intend on using it, read the notes supplied      carefully.       SAMBA1.   + I get an error telling me I have no chroot.        You do not have one :-)   ?     This is simply an informational warning and can be ignored. <     In a future build for OpenVMS chroot() can be aliased to=     invoke chdir() for OpenVMS, so that this message will not      appear.   5     Note that "The Single Unix Standard" published by @     "The Open Group" lists the chroot() function as depreciated.       SAMBA2.   ' I appear to have a trapdoor gid system.   F     OpenVMS does not support setgid().  There is no way to support it.  ?     This is simply an informational warning and can be ignored.   ;     In a future build for OpenVMS, the setgid() call can be >     aliased to a local copy that just remembers the group that;     was attempted to be set, and the getgid() call alias to <     return that group.  This will eliminate that diagnostic.       SAMBA3.   9 Why are some files with double underscores not displayed?   A     The issue with the double underscore has to do with how Samba ?     VMS and Pathworks encode filespecs with characters that are 9     not legal OpenVMS characters on an ODS-2 file system.   ;     Characters that were not legal were encoded with a "__" 7     followed by the Hexadecimal code for the character.   @     As part of this, under older versions of Pathworks, when youA     saved a file from a LANMAN client that had two underscores in >     it's name, the file on OpenVMS would end up with "_5F_" in     it's place.   A     [This treatment of double underscores does not seem to be the (      case with Pathworks 6.0 and later.]  A     The problem with displaying them is that when SAMBA-VMS looks @     up the file and converts/decodes it to a UNIX style name, if@     the double underscore is not followed by a valid pair of hex!     digits, it is passed through.   B     Now what SAMBA-VMS does is read in the filename and convert it?     to UNIX so that the UNIX based code can manipulate the file      specification.  A     Later SAMBA tests the filename with a stat() command multiple @     times after that.  For VMS that requires converting it back.>     When the conversion routines sees the double underscore itB     converts it to "_5F_".  In the case where the original file is<     "__" this results in a file not found error.  SAMBA then     ignores the file.   @     With ODS-2 naming limitations, when file names are converted@     by adding characters, it is not possible that the conversion     will always work both ways.   :     Another filename that is invisible to SAMBA is the VMS;     specification ".;".  It is also invisible to Pathworks.        SAMBA4.    What is ODS-1, ODS2, and ODS-5?e  C     ODS-1 is the name of the file system that is used on the RSX-11 :     family of operating systems.  OpenVMS/VAX can use thisA     filesystem.  IIRC: It is limited to one level of directories,t@     and filenames are limited to 8 or 9 characters followed by a$     period and another 3 characters.  E     ODS-2 is the name that VMS gives to the filesystem that is nativeeD     to it.  Under it filenames are limited to 39 characters followedE     by a period, and then another 39 characters.  For versions of VMS B     prior to 7.2 there can be 8 levels of a primary directory.  InE     addition 7 levels of rooted directories can also be specified, orv#     concealed under a logical name.l  A     For OpenVMS version 7.2 and later, there can be 255 levels ofn     directories.  C     A complete ODS-2 file specification can not be greater than 255s     characters.s  ;     ODS-3 and ODS-4 are CD-ROM filesystems according to then<     "Ask The Wizard" link at http://www.openvms.compaq.com .  C     ODS-5 is new filesystem available for OpenVMS ALPHA version 7.2iA     and later.  It allows longer file specifications and a larger      character set.  C     [I have not tested any version of SAMBA on an ODS-5 filesystem,b*      so I do not know how it will behave.]       SAMBA5.    Did SAMBA-VMS crash my system?  E     Probably not.  SAMBA runs mostly in user mode code, and user modet&     code can not cause a system crash.  E     There is one portion of SAMBA that currently runs in KERNEL mode, A     and that is when the computer changes the effective username.hD     While an error in that section of code can cause a crash, it has7     been in use at quite a few sites for quite a while.h       SAMBA6.;  4 SAMBA stopped working after an OpenVMS upgrade, why?  >     The component of SAMBA that allows the SMBD to change it's?     username while it is running needs to be linked against theo@     system image.  See the instructions for setting up SAMBA and     re-link.       SAMBA7.a  9 Why can clients not connect to my SAMBA server?  (Take 1)c  =     Samba-VMS server currently requires clients to be able too&     connect with plain-text passwords.  8     By default this is disabled for most LANMAN clients.  7     Registry scripts to enable plain text passwords areo<     available as part of the main SAMBA distribution if they2     are not present in the SAMBA-VMS distribution.       SAMBA8.   & What about Windows 2000 and SAMBA-VMS?  8     There are some fixes in the SAMBA 2.0.7 release that3     addresses problems with Windows 2000 and SAMBA.        SAMBA9.o  # What can be done to speed SAMBA up?s       Some general suggestions:M  >     You can try the DCL command SET RMS_DEFAULT/BUFFER_COUNT=N<     where N can be from 1 to 255.  This can also be set with,     a SYSGEN parameter in MODPARAMS.DAT. ex:  7     MIN_RMS_DFMBFSDK = 2 ! Sequential Disk file buffersf    3     Many tuning problems will show up as CPU bound.M  8     Do on all your disks, $SHOW DEVICE/FILES/NOSYS Dnnn:?     Every time that you find the same executable file more thanr>     once, that file should be installed as a shared image with=     the header resident.  This will get you a lot of physicalS=     and virtual memory back.  You may need to increase globalu2     pages and global sections to accommodate this.  =     If you even suspect that an executable may be run in morey:     than one instance, it should be installed.  The second<     activation of most executables that are not installed is     costly.s  >     This will also speed up the launch of your SMBD processes.  9     Avoid all unneeded paging.  For this examine the peakp:     virtual memory used by each process.  Adjust the quota3     for working set extent to match the value seen.t  =     Over allocating WSEXTENT will not hurt you unless you arel!     very severely memory limited.i  @     The SYSGEN parameter WSMAX may need to be increased for your:     system.  Set it as high as AUTOGEN will allow with out4     complaining about hurting working set expansion.  8     This may cause more processes to swap out when idle.;     If this impacts performance negatively, then you likelye;     need more memory for your workload.  Of course the stepm9     above of liberally installing images will help there.r  5     Your NPAGEDYN pool should be set so that there isb9     300,000 blocks free with out any pool expansion while 9     you are running under your full normal load.  This isi;     contrary to what AUTOGEN will calculate, but is part ofd9     the documentation for the DECWindows-Motif and TCP/IPt
     products.a  ;     If you are running OpenVMS 5.5-2 and earlier, make surev3     that you have 1/3 free of the IRP, LRP, and SRPr*     allocations, with out pool expansions.       SAMBA10.   Running TESTPARM gives:a9 WARNING: lock directory /samba_root/var/locks should haven% permissions 0755 for browsing to worka  =     Yes TESTPARM does this.  I have not found out exactly why /     yet, but you can safely ignore the message.        SAMBA11.  7 SMBD takes a long time to transfer a file, and high CPUt utilization is observed.  ;     One cause of this has been traced to a bug in the DEC Ch7     ftruncate() function that has been confirmed by thep:     Compaq Customer Support Center.  At this time there is     no known fix.a  6     The best workaround is to recompile SAMBA with out"     HAVE_FTRUNCATE_EXTEND defined.  8     I have only seen this problem personally on ALPHA so0     I do not know if it affects the VAX version.       SAMBA12.  % Samba is not starting after a reboot?   9     You must make sure that SAMBA_STARTUP.COM is executeda.     after the TCPIP$STARTUP.COM or equivalent.  5     Also for TCPIP or (Substitute UCX if needed) makes9     sure that the last statement in the SAMBA_STARTUP.COMt     has the line:y  "         $TCPIP ENABLE SERVICE SMBD  7     It appears to be needed because some of the logical 8     names used in the service definition are not defined)     at the time the TCPIP$STARTUP is run.l"     [from a post by Jeff Campbell]  7     It appears that the INSTALL.COM routine supplied byn:     SAMBA 1.9.x-VMSn is needed to be run to set up logical6     names that are needed.  It may be needed to be run(     before the TCPIP program is started."     [from a post by Zane H. Healy]       SAMBA13.  ' Any issues with SAMBA in a VMS Cluster?s  ;     It has been reported that SAMBA works fine in a clusterm8     when using common files.  Load sharing is a function6     of using TCPIP aliases and a DNS that supports it.      [From a post by Gus Bingham]        
 PRINTING1.    Printing is not working? (take1)  ?     Printing does need write access to a spool area.  Make surei=     that the logical name TMP is defined at the process level 0     to be SAMBA_ROOT:[VAR], and not SYS$SCRATCH.  ?     Printing takes place in a setuid() section, and the logicalcB     names in the GROUP and JOB tables are not visible to the code."     So SYS$SCRATCH is not defined.      
 PRINTING2.  6 SMBRUN ERROR: Can't find smbrun. Installation problem?@     "Running the command '<print command from smb.conf>' gave 1"  =     The actual string value for SMBRUN that it is looking form=     can be specified in a header file, and then superceded in 
     smb.conf.T  B     The 2.0.3 version of SAMBA uses the string SMBRUN as a default-     if nothing is specified in smb.conf file.a  <     It is also noted that the 2.0.3 version of SAMBA-VMS may+     require the following line in smb.conf:A  '     smbrun = /samba_root/bin/smbrun.comn  @     You do not want to put a path in the smb.conf file, you want     specify a single name.  B     That name must exist both as a logical name that points to theD     command file and as a DCL symbol that defines a foreign command.  ?     The default installation of SAMBA-VMS should configure bothd     of these for you.u  @     If the logical name is missing, the error message above willB     probably be generated.  If the symbol is missing, the printingB     will not work, and other messages may or may not be generated.      
 PRINTING3.  > Why does the job number displayed from SAMBA not match the one displayed by OpenVMS?   ?     The job number for a print job in OpenVMS is an UNSIGNED 32 A     BIT LONGWORD, and can be any valid value for it.  It does notu8     necessarily always increment in a predictable order.     (Just usually does).  A     The LANMAN protocol only allows 16 bits of this job number tot=     be sent, and the UNIX SAMBA code uses the upper 8 bits toh@     contain an SMBD Server instance specific number that maps toB     the print queue.  It is not possible to 100% predict what that     number is.  B     This leaves only 8 bits, for the print job number.  The numberB     returned from OpenVMS or passed to the command files for beingD     processed is only the lower 8 bits, if your VMS print job number     is greater than 255.  A     It also means that the job number viewed from a LANMAN client '     will not match the local VMS value.o  @     In a version beyond 2.0.7, the main samba team is re-writingD     this code, and I have not seen how this will affect OpenVMS yet.       MISC1.  A Can I run a VMS program by double clicking on it from a Microsoftr Windows shell?       Take a look at8     http://www.danbbs.dk/~degnbol/software/rse-0.21.zip.  ;     It is a Microsoft Windows shell extension, starting X11U:     programs on SAMBA shares when they are double-clicked.5     It does not use magic scripts, but rsh or rlogin.w     [Gunnar]  <     [I have no idea if this will work with SAMBA-VMS - John]       FUTURE1.  - Is there a SWAT implementation for SAMBA-VMS?b  B     At this time no.  I (John Malmberg) am working on a 2.0.6 port>     that the SWAT routine compiles and links cleanly.  However>     testing and debugging it is lower on my priority list than/     getting the SMBD serving working correctly.a       FUTURE2.  5 Files get mangled by NOTEPAD and some other programs.   B     This seems to be caused by problems in the ftruncate() or lackA     there of in OpenVMS.  I am looking at various potential fixess(     for this and other related problems.       FUTURE3.  ; Directories with over 10,000 files are not fully displayed.X  B     This seems to be a limitation in SAMBA-VMS where it can not do@     the required processing in time.  It may be a while for this     to be addressed.    