Running Samba 2.0.6 on Alpha VMS

[John E. Malmberg]

"Fachetti, Robert" <fachetti at pweh.company> wrote:
 >
 > VMS Users,
 >
 > I am also having other problems: If I set "security = SHARE", then I
 >  can connect to a service from my PC. But, when I edit a file (for
 > example NAME.TYPE;1) on my VMS share using a PC editor (I have
 > tried this using both Notepad, and the editor in our Ada IDE with
 > the same results) I get the following behavior:
 >
 > Doing a "File->Save" results in: 1. The original file gets
 > overwritten (it does not create a new version of the file e.g.
 > NAME.TYPE;2) 2. The contents of the file are corrupted:

SAMBA being a UNIX program has no knowledge of version numbers, so it 
always will overwrite.

 > Saved Contents:
 >
 > function GET_THE_KEYSTROKE return integer;<CR><CR>p EXTERNAL =>
 > "get$keystroke");<CR> <CR>w<CR> h UIM_TOOLS;<CR> function
 > GET_THE_KEYSTROKE return intbegin<CR> <CR> <CR> TOOLS<CR> <CR> turn
 >  integer(UIM_TOOLS.GET_KEYSTROKE);<CR> end <CR> T_THE_KEYSTROKE;<CR>
 > teger(UIM_TOOLS.GET_KEYSTROKE)<CR>
 > <CR>
 > end GET_THE_KEYSTROKE<CR>
 > <CR>

Sometimes NOTEPAD saves a file over the old one, and sometimes it 
creates a temp file, deletes the old, and then renames it.  I have not 
figured out that rule.

I thought I had that problem fixed.  But apparently not.  Is the 
behavior different if the file is in the root directory of a share than 
it is when in a subdirectory?

Also what created the file originally?  That may make a big difference.

The <CR> is from the PC program saving the file as <CR> delimited file, 
and UNIX knows that it should be saved as a <LF> delimited file, so the 
resulting file attributes are wrong.

This is also the way it works on UNIX as people on the UNIX SAMBA forums 
have complained about it.

If you look in the some of the documentation notes that came with the 
SAMBA 2.0.6 for OpenVMS kit, you can force SAMBA 2.0.6 for OpenVMS to 
set the file header to match the type for the extension when it creates 
a file that does not have a previous version.

If it has a previous version, the existing attributes are inherited by 
the new file.  This could be what is causing the corruption you are 
seeing if the file was originally created by an OpenVMS editor.  But 
that still is a bug.

I posted just a little while back, the file attributes that would 
probably get rid of the <CR>, but can not remember them off the top of 
my head.  It is either STREAM-CR or STREAM-LF.  It is late here right 
now, so I do not have time to look them up.

-John
wb8tyw at qsl.network
Personal Opinion Only