Subscription information advice
If you are trying to subscribe to the SAMBA-VMS mailing list, you need to follow the instructions at the SAMBA.ORG mailing list web pages. Sending subscription requests to the mailing list just go into the spam filter, which means that they will probably be deleted unread. Also if you send the request with an e-mail address of a free e-mail provider, then use that e-mail providers mail servers to send the request. The free e-mail providers have set SPF (Sender Policy Framework) entries that state explicitly that only their e-mail servers are allowed to send e-mail from them, and that e-mail from all other sources claiming to be from them should be considered spam and rejected. So if you send an e-mail claiming to be from a hotmail.com e-mail address and use a mail server is not a hotmail.com or msn.com mail server, do not expect there to be any response to it. The same is the case for any of the other well known free e-mail addresses. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba 2.2.8 for OpenVMS VAX 7.3 Vaxstation 4000/60
Luiz Guilherme Regis Emediato wrote: Hi, This command is commented out in SAMBA_STARTUP.COM which is run inside of SYSTARTUP_VMS.COM. I have them installed and if I remove the comment sign it works fine as a work around. However the problem with TCP/IP remains, that is, why didn't the ECO patch resolve the problem with set config enable service smbd set config enable service swat ? Because until the SAMBA_STARTUP command file is run, the logical names required by SWAT and SMBD do not exist. The SAMBA_STARTUP.COM procedure must be run after the startup procedure for the TCPIP services. If you enable the services with SET CONFIG, then all attempts to start the SMBD services will fail until the SAMBA_STARTUP.COM is run. You also may end up with data corruption because some files may not be properly initialized. -John [EMAIL PROTECTED] Personal Opinion Only -- Need a senior system engineer? I am looking for employment. http://encompasserve.org/~malmberg/MALMBERG_CS1_RESUME.TXT PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba-vms file versions
dhruva wrote: Michael Ober wrote: No. VMS is one of the few, if not the only, file system that supports versioning. As a result, no version of Samba support versioning. To add to this response: Samba in it's current form does not support this feature. However, using the VFS layer architecture that Samba follows, this can be implemented. Once you over ride the readdir() in the VFS layer, you should be able to see all the versions from the windows client. The deluxe way of implementing such a feature would be for a VFS layer in SAMBA to read a file somewhere in the directory tree of a share that indicates how the files are to be served. XML would probably be a good format for that file, and by default it would have a hidden attribute. Then an extension to the Windows Explorer could be written that would allow the configuration file to be modified through the folder properties. There are plenty of examples of these types of extensions, so it does not look like it would be too hard to implement. One thing to consider is how the versions should be represented to the client system. The closest convention to what PC based programs do now would be to put the version number in () such as (100) at the end of the filename. And of course no version number present for the top version. Options for this could also be stored in the configuration file. At this point, while I would like to personally look into adding such a feature, it is not likely that I will be. I am leaving HP and am now in a full time job search. I have passed on the information to Dhruva for building Samba V4 on VMS for a followup for after the V3 version is feature complete. If you want to experiment and influence where SAMBA is going, Samba V4 is what you need to be building. Building SAMBA V4 requires the latest GNV kit, PKG-CONFIG, Blead-perl, and a specially modified Perl 5.8.7 kit, and GTK+ 2.x with it's components. For SAMBA V4 to run, it will require components that Dhruva is now integrating into the V3 version for OpenVMS, and I have not yet added those components to my SAMBA V4 build. I have not yet run any SAMBA V4 binaries, and I will not be able to assist others in setting up a SAMBA V4 build environment on VMS until after I get settled in a new job, assuming that then time permits. -John [EMAIL PROTECTED] Personal Opinion Only http://eisner.encompasserve.org/~malmberg/MALMBERG_CS_RESUME_2006.TXT PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: HP Port and EXTAUTH
Michael Ober wrote: Is HP adding their Pathworks EXTAUTH module to their Samba Port for VMS? It is in the current plans to support external authentication with OpenVMS CIFS instead of Advanced Server. The exact method is still to be determined, as alternative implementations are being looked at, including using LDAP to communicate with an active directory server. Such a implementation may not even require OpenVMS CIFS to be installed. Has anyone tried configuring the Pathworks EXTAUTH module to reference a SAMBA based domain controller? -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Problems starting nmbd
Ryan Lolli wrote: I just installed HP OpenVMS Common Internet File System (CIFS) and when I execute any commands I get the following error. Does anyone know how to fix this? unknown_domain_COLA$ testparm %DCL-W-ACTIMAGE, error activating image SECURESHRP -CLI-E-IMGNAME, image file $1$DGA1534:[SYS1.SYSCOMMON.][SYSLIB]SECURESHRP.EXE -SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image That message usually indicates that you are attempting to run HP OpenVMS CIFS on a version of OpenVMS earlier than 8.2. If you are running OpenVMS 8.2 or later, then you may be missing an ECO kit. Please send the details of what ECOS are installed to the OpenVMSCIFS(at)hp.com e-mail so that HP can determine what dependencies. If you are not running OpenVMS 8.2 or later, then this is the expected message. However it also indicates a bug in the PCSI kit not specifying a minimum OpenVMS version. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: The HP version of Samba ....
Ross Smith wrote: A quick question to the list: Has anyone installed HP's alpha release? Yes. Does it work of any of you? It is somewhat functional, but there is a lot of work still needed on it. It was in use at the OpenVMS bootcamp and was used to serve the presentations. I do not think that was generally announced. If you have provided feedback to HP, did anyone ever get back to you? In my case I installed the updated release for Itanium and it works up to a point: the point being that it does not report the disk size correctly and so I can't save files to disk (which has zero free blocks). This issue has been traced down to a bug in the C library routine statvfs() which is working on traditional OpenVMS file specifications, but failing on UNIX format file specifications. A fix in the C library is being worked on, but I do not know when it will be released. As some client applications check for free disk space, this tends to be a problem. Also, it does not allow you to connect to your home directory. I would recommend temporarily increasing the logging level for the SMBD process to get more detailed information. Somewhere between -d4 and -d8 should provide enough information. If you need help interpreting the log send it to OpenVMSCIFS(at)hp.com. Please try to keep such logs or log fragments small. Also when sending log fragments as attachments, please name the attachment to have the extension of .txt. There are apparently several mail clients / content scanner that do not pay attention to the mime tags and only go by the extension. Please do not post fragments of such log files on a public forum as they can contain sensitive information that may not be obvious because of the way it is encoded. Currently the same logical names are used for this as with the 2.2.x releases. $define/system SAMBA_SMBD_OPTIONS -d4 So this makes it fairly broken, but an attempt to provide feedback to HP got no response. I will be making inquiries about why there has been no response to your feedback reports. You are sending them to the proper e-mail address, and they are flagged for a follow up. -John [EMAIL PROTECTED] John.Malmberg(at)hp.com Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba v3 on VMS and HP VMS Roadmap
Michael D. Ober wrote: To the VMS engineering team, is this still accurate? http://h71000.www7.hp.com/network/CIFS_for_Samba.html If so, will password synchronization and external authentication features be implemented? As I understand it, it is in the plans for the production release. I do not think those features will be ready for the evaluation release. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: smbd purpose?
Dr Robert Young wrote: With guidance from some people on the list, I was able to get the smbpasswd set correctly, and I can access my VMS directories now. However I have a question In my tinkering I had issued a TCPIP SET NOVERV SMBB as part of my efforts to clean out things between install attempts, and had not set it up to run again ( I forgot :- } ) The SMBD service needs to be enabled from TCPIP. What happens on VMS is that the TCPIP service dispatcher listens on port 135 and when it gets an incoming connection request, it starts up the SMBD process as a response. After the session is over, the SMBD process lingers for a short time in case another connection comes in from the same source, but if it does not, it will terminate. I can not easily read the docs on samba 2.2.8 (8/17/2005) since they are all HTML (I am working on a VT320 ). LYNX is available for VT320s, but that really does not make it much easier. In the VMS kits 2.2.x, many of the the internal links are all wrong because they are set for UNIX pathnames with multiple dots in them. The documentation for 3.x is not that much different from the 2.2.x version and is available at the SAMBA.ORG web site. There is not much in the way of VMS specific documentation. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba configuration file for VMS
George Blum wrote: I am new to Samba though not to VMS. I need some help in setting up the configuration file for Samba. I am running VMS 8.2 and have the latest Samba compiled and installed. My questions are The term latest is ambiguous. There is a 2.2.12 release in the wild that is missing some of the latest 2.2.8 OpenVMS specific changes. And there are several versions of 2.2.8 out in the wild from various sources. The distributions now have a date encoded in then, and a check of http://www.pi-net.dyndns.org/anonymous/jyc/ shows that the latest is 20050817, which means it has a few more VMS specific changes than the 2.2.12 version at: http://eisner.encompasserve.org/~malmberg/samba/ 1. How do you tell samba which disk to serve? i.e if I want to serve disk dka100:[00] what do I put in the config file? /dka100/ Putting in the 00 may or may not break things, but should not be present in a translated name. A better name than /dka100 would be one of the logical names assigned by the mount command, like /disk$user_disk1. DKA100:[00] might work, but also may not. I have not tried it with the 2.2.x version. Ideally it the configure file should support concealed rooted logical names and VMS syntax. I generally restrict the use of physical device names only to the few utilities and commands that must be done on them. It makes managing and using a large farm of VMS systems easy when I can depend on the user files being in user_root:. By using concealed rooted logical names, I can upgrade a systems with different numbers and types of disk devices with out having to ever change an application setting. Applications that store physical device names in their configuration files are in conflict with efficient system management. 2. If I want samba to use the authorize file for login passwords, what do I put in for passwod? That requires that you disable encrypted passwords on your clients. Otherwise you need to use the smbpasswd program to create the initial password, and your users need to use it to change them. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: dots in directory names of shares on ODS-5 disks]
BG - Ben Armstrong wrote: Also, I still don't understand why a workaround is not possible. If there is no workaround, several otherwise useful Unix applications (Subversion is the one I'm interested in today, but there are others) cannot operate on Samba ODS-2 shares because they heavily rely on files kept in directories with dots in them. The filename translation routines in SAMBA 2.0.6 could certainly deal with the extra dots in the directories. ODS-5 does not need any of the filename mangling, and should not need any special casing. And nothing in the SAMBA source code really needs ODS-5 filenames, the proper solution is to make the filename support on OpenVMS to be two VFS modules. I recall only one case where SAMBA 2.X is using a filename that is not compatible with ODS-2, and per the SAMBA coding practices, it is a bug because those filenames should be set in the CONFIGURE, with a default value if they are not set. I have not checked if that bug is fixed in SAMBA 3.x, but if not, it is something that a patch can probably be written for that they will accept. One For ODS-5 which basically will not do much, and one that has all the work arounds for ODS-2, and this would be designated by a share parameter. Right now, one of the hassles in the filename mangling is identifying if the volume based on the given pathname is ODS-5 or not, and that requires either keeping track of the default device, or otherwise looking up the information on the fly. The VFS approach simplifies all of this. The VFS approach also would make it easy to add a VFS that exposed multiple versions of a file for some shares. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Alpha OpenVMS 8.2
Michael Ober wrote: Does the May 31, 2005 release of JYC's Samba 2.2.8 support OpenVMS 8.2 on Alpha? You will probably need to recompile and relink it. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Out of Office AutoReply = Security Risk to Your Company.
Folks, Convicted criminals have stated that they use these messages on phones and probably now e-mail to steal from companies. They have stated that the easiest way to steal from a company is to impersonate the identity of someone known to be out of the office. Some of these criminals have made the headlines of the traditional press with these exploits because the thefts have been with very high amounts. IIRC: On U.S. TV, a demonstration was done where the tester was able to get the dialup phone numbers and a senior (VP level) employee's login account and password reset, all the while that the employee was trying to demonstrate that their system was secure from skilled hackers on that same TV show. Secret prototypes have been stolen, along with confidential documents. And the dollar amount has been in the high thousands, if not in the million dollar range from just one of these criminals. I strongly recommend just turning off the out-of-office feature completely. In addition to the security problems, these messages will auto-respond to forged addresses in spam and viruses, and this turns your mail server into a participant in a denial of service attack on the rest of the Internet. Most corporate mail systems allow mail to be temporarily read by a secondary trusted user. Use that method instead. If you have any influence with the security policy of your company, get these auto-responders banned, and the same for having any phone messages that indicate how long your identity can be spoofed with no one at your company being able to easily reach you. Essentially these messages are now the same as not stopping your news and mail delivery while on vacation. And mailing list traffic is clearly marked so in the headers, so any auto-responder that responds to them is not compliant with RFC standards. In addition to the messages to this list, I got two messages from broken auto-responders from my last post. -John [EMAIL PROTECTED] Personal Opinon Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: [Samba] Re: nazi spam in German over list address
Daniel S. Haischt wrote: Basically if re-training your SPAM filter does not help and one really wants to get rid of all those junk mails, installing a challenge/response system like TMDA behind a statistical filter (e.g. DSPAM) would be a possible solution ... No. All that a challenge response system would do is add a bunch of challenges to forged addresses to the mess that the worm is creating. It is hard enough to filter out this worm from all the infected hosts, but realize that the list operators are also having to try and filter out all the things that are incorrectly auto-responding to the forged address. Challenge response systems are a plague to mailing list operators and to any mail server operator who has had their domain forged by a virus or a spam run. Many of the mail server operators that I know are now blocking on sight any user and/or network that is using any Challenge Response system that they receive a mis-directed challenge from. My e-mail address is now under attack from mail servers that are not using SMTP rejects. All challenge response would do is increase the amount of junk that is now coming in to it. The same would happen to these lists. Right now there should be filters in place that know about most of the subject that this particular worm uses. -John -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
I think it should be clear, at least for a while.
The filters have been adjusted. From looking at the Samba lists, this one was the least affected by the sober worm that is spamming in German. I see only one instance made it through here. Some of the other lists were mailbombed, and are now getting mis-directed bounces from mail servers that are not using SMTP rejects. Fortunately most mail server operators know only to use SMTP rejects for undeliverable mail. Feel free to file individual abuse reports to any of the mail servers that are generating virus detected spam and undeliverable message spam to known forged addresses, as this is the only way that they will get feedback on how abusive that behavior is and that sending such messages is participating in a global denial of service attack which is assisting the virus writers and spammers. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Samba 2.2.12? (was: Disk share size reporting error?)
Ross Smith wrote: On Apr 12, 2005, at 12:50 PM, COLLOT Jean-Yves wrote: could someone please post a couple of lines saying what the latest release(s) are for VMS and where they can be obtained. OK, I think I can answer that. The version 2.2.8 is currently available for download at http://www.pi-net.dyndns.org/anonymous/jyc/ John E. Malmberg has mixed the 2.2.8 port with the Unix 2.2.12 version, and has done a number of changes/enhancements, mostly to support VMS 8.2 and IA64. This is very helpful. Thank you! In fact I do have a IA64 box and so for me, maybe, the 2.2.12 version may be the best bet if I'm starting from scratch. I had hesitated in part because at some point I think John said that he had not incorporated the fixes you'd made in 2.2.8 into his version. I have not had time to merge Jean-Yves latest changes in. Feel free to do so, I do not think it would be a big change. Samba3 is very close to Samba2 in architecture if you want to go that route. Samba4 is where all the new development work is going on. Currently neither Samba3 or Samba4 ports for OpenVMS are known to be available. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Problem with authentication for samba 2.2.8
Herriot, Nicholas, VF UK - Technology (TS) wrote: Hello SAMBA team, I've installed and setup a samba server 2.2.8 from binary's and following install instructions on a: OpenVMS V7.2-1 on node WINDE1 Verify you have the lastest kit. From windows NT. with service pack 3 I can see the node WINDE1, but when I try and access the machine authentication always fails, no matter who simple and open I make the smb.conf file. I've even tried setting up a guest user, encryption on, I've setup a new smbpasswd file, then changing the password using the smbpasswd.exe program. But nothing seems to work. Anyone can give me a clue plseee help! My SMB.CONF file looks like: snip The only errors I can find are below, but I've no idea how to solve them. cheers in advance to anyone who can help... stm_open: open /samba/private/MACHINE.SID, flags , fd = -1 [2005/03/13 19:10:27, 1] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_8-SRC.SOURCE.VMS]STM_REA D.C;165:(323) stm_open: open /samba/private/smbpasswd, flags , fd = -1 [2005/03/13 19:10:27, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_8-SRC.SOURCE.PASSDB]MACH INE_SID.C;2:(163) pdb_generate_sam_sid: Failed to store generated machine SID. [2005/03/13 19:10:27, 0] DISK$SWAP:[JYC.SAMBA.SAMBA-2_2_8-SRC.SOURCE.SMBD]SERVER .C;27:(907) ERROR: Samba cannot create a SAM SID. WINDE1$ My guess is that a directory may be missing where it wants to store the SID file. Try increasing the error level for the SMBD process. As I remember things, this can be set by a logical name. -John [EMAIL PROTECTED] PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Vim detects a file on a VMS Samba share has changed when it has not
BG - Ben Armstrong wrote: I am using Vim on Linux to edit files on a Samba share on VMS. I am finding that it detects a file has changed when it has not. That is, the following dialog box appears a couple of minutes after I start editing: W12: Warning: File /dyma/s/dymax/020005/bg.tas has changed and the buffer was changed in Vim as well See :help W11 for more info. Here is a dir/full of that file on VMS. Perhaps a significant detail is that the file is owned by [DV.BH] whereas I am [DV,BG]. Also, I have seen the same dialog box appear when the text file is a Stream file, so I don't think the fact that it is a Variable file has any bearing on the problem. snip Any ideas as to what could be wrong? Further tests I could do to narrow down the possibilities? Unless a special case has been put in the latest OpenVMS port, what you are seeing could be an artifact of a different behavior between UNIX and OpenVMS. In the 2.0.x versions, SAMBA always opened a file for read/write access, even if read access was requested. This was related to how SAMBA handled lock requests. Apparently there was an issue if the client changed from read only to write access. On UNIX, the file modification date is only changed if the actual file was changed. On OpenVMS, the file modification date is updated because the file was opened for write. There may be some DECC$ feature logicals that can affect this on ODS-5 volumes. I put a hack in on the SAMBA 2.0.6 to deal with this issue. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Error in the compilation of Samba 2.2.8
Plante, Sylvain wrote: OpenVMS Samba users, Here's the list of error coming in compiling ( build) the latest version of Samba. It is compiled on : OpenVMS 6.2-1H3 DEC C compiler V5.7-004 Can you try a newer compiler? The HP (DEC) C compiler for VAX is now at version 6.4 and I think that it should work on the older versions of OpenVMS. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba for OpenVMS 6.2-1H3
Plante, Sylvain wrote: SMB-OpenVMS users, I'm looking for a version of ( Samba 2.2.x ) which would be running in OpenVMS 6.2-1H3 . The latest version on the web site specifices that the prerequistes is OpenVMS 7.1 . Is there any Archive site where I can find what I'm looking for ? You can try building the 2.2.8 version and see how far you get. I see a lot of things in the source code that is only needed for it to build on the 6.x or even 5.x releases of OpenVMS. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
URL for mailing list seems to have changed.
David Gudewicz just gave me a heads up: The URL for the mailing list seems to have changed and the old one no longer works. I do not know if this is a bug or a permanent change. The current working URL is: https://lists.samba.org/mailman/listinfo/samba-vms -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: SAMBA V3 and beyond.
BERAMICE, Frantz wrote: Hello, Do you know if samba v3 for VMS is in the pipe ? I know of some people looking at it. I am personally more interested in looking at SAMBA V4. Work on SAMBA V2 for UNIX except for security bug fix releases essentially stopped well over a year ago, and probably over 2 years ago. With SAMBA V2.2.12, the SAMBA team has announced that it is the last of the Emergency patches to the V2 stream, which makes it the proper landing spot for systems that are currently unable to move to V3 or beyond. The only real difference would be a few more LANMAN subprotocols would be supported. Most of the new features that are available in SAMBA V3 are based on features that are conditionally compiled out of the SAMBA V2 port. There are not many differences in structure, so in theory, you could just take the current OpenVMS specific code and merge it with the SAMBA V3 code base, and it would likely work about the same as what SAMBA V2 does now. Work on SAMBA V3 for UNIX is now winding down, and plans are for it to be effectively frozen as soon as SAMBA V4 is viable. Essentially starting work on a production quality and full featured V3 port for OpenVMS needed to have started over two years ago in order for it to have any functionality better than what you have now with V2. The main purpose of doing a V3 port attempt is to identify the UNIX/LINUX APIs that are not currently present on OpenVMS and need to be, and to look at changing the way the current OpenVMS specific hacks are done to be done the way that is defined in the existing architecture for LINUX/UNIX extensions. This work is also required for V4, but would likely be significantly longer before they could be tested on V4. If you do not need a production quality server in a hurry, and need to learn how it all fits together, starting with V3 as a learning experience is the way to go. And there is no reason that the same things can not be done with the V2 port to activate most of the same functionality, which would directly carry over to V3 and V4. The issue right now is that the main SAMBA team is not interested in patches to SAMBA V2 at all and has mainly only been interested in emergency security patches for at least the last year, and there may only be a year or so left that they will be able to be convinced to accept changes to V3 that would make the UNIX code work better on OpenVMS. SAMBA V4 is a new design that has not yet been fully finalized, so it may be possible to find ways to make it fit better with an operating system that does not fork(), and there are more of them interested in using SAMBA than just OpenVMS. One of the issue on how to proceed is how to coordinate the efforts of all the volunteers and potential commercially supported programmers into one effort. I have not even been able to convince Jean-Yves to move to 2.2.12 as the final landing point for the V2 stream, and I have not had time to merge his changes into the 2.2.12 kit that I have previously posted a link to. It appears so far that SAMBA V4 may require at the minimum GNV and some flavor of Perl in order to build it. -John [EMAIL PROTECTED] Personal Opinion Only -- Please address all SAMBA-VMS related replies to this forum for public discussion. PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: SAMBA for OpenVMS
Tony Naidoo wrote: Folks I would appreciate your help... DSA1:[KITS.SAMBA-2_0_3.SOURCE.VMS]VMS_SUP.C;134:(561) vms_mkdir: /samba_root/private/, mode: 700 COLLOT Jean-Yves wrote: There is a new release available of Samba/VMS 2.2.8 at http://www.pi-net.dyndns.org/anonymous/jyc/ Please read that page to know about the changes/fixes of that new release. For one thing, you have commented out required [unique_tag] for the share name that is used to separate the shares. ; A publicly accessible directory, but read only, except for people in ; the staff group [public] comment = Public Stuff path = drb1/ris/mar/dg1/in public = yes writable = no printable = no write list = @staff I have never used the write list parameter. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Settings problem?
Ross Smith wrote: I'm very new to Samba. I ran an install this morning and have 2.2.8 running on a IA64 OVMS v8.2 machine and I'm still figuring out what end is up... Unless you have gone through the source, you may find that parts of SAMBA think you are running on a VAX. I noticed on the Mac OSX.3.8 box I used to test the server that I have a zero -length file on the server... -rwx--1 smithp01 admin 0 Dec 1 16:03 smithp01-1/mdp.bck Actually, on the VMS side things are rather different ... Directory SYS$USER:[SMITHP01] mdp.bck;1 501291/5012961-DEC-2004 15:54:20.18 Presumably there is a size overflow issue here for the directory. More likely a different bug. The size field data type is more than large enough for the task. Is there a fix? or a different choice for parameters in smb.conf? I do not know. Which 2.2.8 release are you running? There have been several of them. I do not know what if any of the things that I changed for 8.2 and IA64 on http://encompasserve.org/~malmberg/SAMBA/ in the SAMBA 2.2.12 kit have been incorporated in Jean-Yves latest kit. I do know there are fixes in Jean-Yves latest 2.2.8 kit that I have not yet rolled into 2.2.12. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: naming like xxx.5_htm
gérard calliet wrote: Hello, Where can I find documentation about the choice of naming htm files from the documentation set in the form xxx.n_htm ? The archives of this list, back on September 9, 2004. The choice was made by the DETAR or UNZIP tool when it encounters a filename that can not be represented on an ODS-2 file. And how configure a browser to follow an associate link in a form xxx.n.htm ? It would likely require rebuilding the browser to handle ODS-5 file specifications, including directories. MOZILLA does not currently handle them. https://bugzilla.samba.org/show_bug.cgi?id=1763 The VMS port of SWAT has special case code to handle the current naming, and that would have to be changed if the names were made to comply with ISO-9660 or with what the web browsers on OpenVMS can deal with. ISO-9660 requires an 8.3 naming convention unless the host operating system can deal with extensions to the standard. I would recommend someone putting together a script/program to fix the filenames and links to an iso-9660 compliant format, and change SWAT to also deal with that. The ideal would be if the producer of the SAMBA documentation would make the output comply with ISO-9660. Alternatively all the tools to convert the raw SAMBA documentation to HTML and other formats seem to still be available on OpenVMS in one form or another, it is just a learning curve to package and use them. If anyone wants to volunteer... -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Different times on VMS and Windows for a file
Michael Mazzoni wrote: Environment: VMS v7.3 on an Alpha, Samba-VMS v2.2.8. 1) is this a Samba-VMS problem? Yes and No. The code that uses that logical only needs to exist on binaries for OpenVMS 6.x and earlier. There is no reason to use those routines on current versions of OpenVMS. It is quite probable that the test is not even needed with the current sources. I would have to review the source to verify. 5) searching all the .c files in v2.8.8 doesn't find SYS$TIMEZONE_RULE, so how is the time differential handled? By the UTC routines in the CRTL. The usual reasons for the logical being missing after a reboot, is that DECNET-PLUS is running, but DTSS has not been disabled through use of the feature logical name. This is done in the SYS$STARTUP:NET$LOGICALS.COM file which is created from the NET$LOGICALS.TEMPLATE file. If the logical name is not defined on a DECNET-PLUS system, the timezone logical name is not created at boot, but will be manually created by running the timezone configuration. See the Timezone information in the VMS System Manager Guide and in the FAQ. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: SAMBA startup + shutdown
Albrecht Schlosser wrote: Hi, here are some minor problems I found with Samba startup and shutdown, using Samba 2.2.8, release 2004-1021 with SAMBA_SHUTDOWN.COM by R. Regier 15-Sep-04: (1) The shutdown procedure disables the services SMBD and SWAT. This is useful (only) if you want to (temporary) disable the service(s) on a running system and start them later again. The unmodified procedure SAMBA_STARTUP.COM does not enable the service, because they should be enabled by the TCPIP startup procedure. However, this is not true, if you run SAMBA_SHUTDOWN.COM for any reason and want to start the service again with SAMBA_STARTUP.COM. I'm not sure what would be the best solution, but for now I decided to uncomment the enable service commands in the startup procedure. Maybe it would be a good idea to add SAMBA_STOP.COM and SAMBA_START.COM (or similar) to stop and start Samba temporarily ... Uncommenting the enable service commands is probably the best solution. Note that until something like the SAMBA_STARTUP.COM procedure makes the SAMBA_ROOT logical name available, TCPIP services can not enable the SMBD and SWAT processes. So unless you have the enable service commands or something else defining the SAMBA_ROOT logical, after a reboot, SMBD and SWAT will not start. (2) One bigger problem with this release (and previous 2.2.8 releases) is the fact that the NMBD process creates the file samba_root:[var.locks]nmbd.pid and checks this file when started. NMBD exits with the following error message in the file SAMBA_ROOT:[VAR]LOG.NMBD: That is also a problem with SMBD. The solution that I did with the 2.0.6 release was change the code to not create a PID file at all. My solution is to add these lines to SAMBA_SHUTDOWN.COM: $ SECTION3: $! $! delete obsolete .PID file ... $! $if f$search(samba_root:[var.locks]nmbd.pid).nes. then - delete/log/noconf samba_root:[var.locks]nmbd.pid;* $! $ ECHO [ Finished NMBD process termination ] A similar check is needed for SMBD.PID. The PID file stuff can also be an issue in a cluster with a common SAMBA_ROOT: (the first and last lines are from the original procedure). Is there a way to stop NMBD in a safe way that it can delete the .PID file? If not, then I think that the check should not be done (under VMS). Setting the process name to NMBD is safe enough if the UIC group of the NMBD process is known. Using the SYS$FORCEX procedure may do it. Or may be configured to be able to do that. But the PID file concept is useless on OpenVMS. If you want to make sure that only one copy of a program is running on a single node or a cluster, the SYS$ENQW call is the only way to reliably do this. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba authentication on OpenVMS using SYSUAF (how?)
Dave Pampreen wrote: Hi everyone, First off, this is my first post, so be nice :) Background: OpenVMS 7.2-1 (Alpha) TCP/IP 5.3 (TCPIP_MUP V5.3-181) installed Samba 2.2.8 (from source: SAMBA-2_2_8-OBJ-20041021.ZIP) I have it configured and I can connect, but I had to use SAMBA_ROOT:[BIN]SMBPASSWD to set a password. What I would like to do is get it so authenticate against SYSUAF so I don't have to maintain 2 passwords. What do I need to do with my SMB.CONF file to accomplish this? Have you enabled plain text passwords in your client? The only way that a LANMAN client can be authenticated against the SYSUAF is if it presents the password in plain text over the wire. The sending of the password in plain text by Microsoft LANMAN clients has been disabled for quite a while. Other than that, I have not tested that configuration. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: DoS Flaws Found in Samba Module
B. Z. Lederman wrote: On the odd chance people haven't seen this: http://www.eweek.com/article2/0,1759,1728956,00.asp German security researcher Stefan Esser has discovered multiple vulnerabilities in smbfs, the mountable SMB (Server Message Block) file system for Linux. The smbfs program is only available on LINUX at this time according to the SAMBA documentation. The other security advisory mentioned only applies to SAMBA 3.x, not 2.x. http://security.e-matters.de/advisories/132004.html -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
RE: SAMBA stopped working
In article [EMAIL PROTECTED], Tillman, Brian (AGRE) [EMAIL PROTECTED] writes: John wrote: This may or may not be an issue. I have not looked totally at this, but I think it is how LANMAN usernames that can not be represented on the host OS are mapped to host usernames. Here's the contents of my USER.MAP: tillman = tillmabg tillman I do not see the code in the smb.conf that enables the use of the guest account if the account does not exist, What would this code look like? map to guest = bad user so my next guess is that in this map file, it maps the Administrator account to something. See above. My guess is that the password for that Administrator account must be in the SMB PASSWORD database, and if you change it on the client system, it also must be changed on the host, if you are not passing through the authentication to a domain controller. The only password in the database is my own and I can't get Samba to recognize it any more. When some clients connect to SAMBA, they first connect as Administrator to get a list of shares, and then connect as the logged in user. If you do not have the Administrator mapped to a VMS account and for a standalone SAMBA installation, have the LANMAN password for it in the Samba password database, then the only other way for the Adminstrator account to get a list of shares is to use guest access. Otherwise the access will fail. You have so far indicated that you do not have the map to guest parameter set, nor do you have the Administrator account mapped. One of them seems to be a requirement. I changed nothing. The other possiblity is that one or more of the databases that SAMBA uses have gotten corrupted. Setting the log level for the SMBD up to 4 may give better information as to what is wrong. Some of the tools in the SAMBA_ROOT:[BIN] may also help do the diagnostics. I have not had the chance to look at most of them though. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
RE: SAMBA 2.2.12 source kit for 8.2 (and possibly earlier)
In article [EMAIL PROTECTED] , Tillman, Brian (AGRE) [EMAIL PROTECTED] writes: Does this port require FRONTPORT and your previous port did? The READMEs in that directory don't mention 2.2.12. It does not use FRONTPORT. The readmes are left over from SAMBA 2.0.6 because I thought that they may have some information that may be of use. I have not had time to clean them up. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
RE: SAMBA stopped working
In article [EMAIL PROTECTED], Tillman, Brian (AGRE) [EMAIL PROTECTED] writes: Brian Tillman wrote: Here's my SMB.CONF file. This was working before and I haven't changed anything on the VAXes except for stopping and restarting the NMBDs:=0D Can someone tell me if my SMB.CONF file is properly configured for= authenticating against the UAF? It sounds like the guest account validation is not working. Some functions effectively will not work with some clients with out the guest account configured and the smb.conf set to map bad users to guest. The last time I chased down this issue, the guest account needed write access to it's own directory and to the TMP: directory which SAMBA 2.2.8 assigns to SAMBA_ROOT:[TMP]. Older SAMBAs have used SAMBA_ROOT:[VAR]. -John [EMAIL PROTECTED] Personal PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: SAMBA stopped working
Tillman, Brian (AGRE) wrote: A few months ago, SAMBA V2.2.8 on my three VMS system (two OpenVMS VAX V7.2 and one OpenVMS Alpha V7.3-1) stopped working. Since I'm the only one actually using SAMBA connections to the VMS systems, I didn't bother to investigate. Today I decided to, but before I did, I updated the Alpha only to the most recent V2.2.8. On the Alpha, I noticed that the SMBD service in TCP/IP was disabled, even though TCPIP SHOW CONFIG SERVICE showed it as enabled (i.e., should start on demand). I enabled the service and restarted NMBD. The NMBD processes on the VAXes were already running. There is a race condition on boot if you do not disable the SMBD service on shutdown, and a client tries to connect to it on startup before the SAMBA_ROOT logical is defined. $ define SOCKETSHR UCX $! $set ver $ arch = f$getsyi(ARCH_NAME) $ nmbd :== $samba_exe:nmbd $ opt = f$trnlnm(SAMBA_NMBD_OPTIONS) $ nmbd -d1 -i Netbios nameserver version 2.2.8 started. Copyright Andrew Tridgell and the Samba Team 1994-2002 standard input is not a socket, assuming -D option I don't know if that last line is normal. It is. It indicates that it was not started by the INETD process. Here's my SMB.CONF file. This was working before and I haven't changed anything on the VAXes except for stopping and restarting the NMBDs: [global] workgroup = Swdev dead time = 10 map archive = no load printers = no security = user default service = default create mode = 0777 server string = %h running Samba V%v (SWDEV) username map = /samba_root/lib/users.map ^ This may or may not be an issue. I have not looked totally at this, but I think it is how LANMAN usernames that can not be represented on the host OS are mapped to host usernames. I do not see the code in the smb.conf that enables the use of the guest account if the account does not exist, so my next guess is that in this map file, it maps the Administrator account to something. My guess is that the password for that Administrator account must be in the SMB PASSWORD database, and if you change it on the client system, it also must be changed on the host, if you are not passing through the authentication to a domain controller. With out setting the Map to guest parameter that Jean-Yves pointed out to me about a month ago, the guest account basically does nothing. Did you change the Administrator account about 2 months ago? -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: SAMBA 2.2.12 source kit for 8.2 (and possibly earlier)
John E. Malmberg wrote: SNIP I dropped a few lines from the previous post. I have only done a test build on OpenVMS ALPHA 8.2 EFT at this time. I attempted to make this code build on older versions, but as yet I have not had time to do any test builds. If it is found not to build/work on a release before 8.2 EFT. Post on the SAMBA-VMS list the fix, and I will attempt to incorporate it into a future source code drop. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: SAMBA share access problem report (Dymaxion 17=17275)
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: Now that I know that the problem appears only when the McAfee antivirus is there, I could fix it. I am sending a corrected version of the OBJ files directly to Rod, a DIFF of the sources directly to John, and I'll include the fix in the next release. Thanks. Note that the .st_nlink field with OpenVMS 8.2 now has valid data, and may now or in the future have link counts greater than 1. I do not know if any of this will show up in ECO kits for earlier versions. I also do not know as I have not checked the source or done tests to see if older versions of OpenVMS have valid data. Before setting the link count to 1, I would recommend testing first to see if it is zero. Support for symbolic links is being phased in, and some parts of it are already present. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: bug: vms_opendir - strcpy can not be used for overlaping moves.
John E. Malmberg wrote: In the module VMS_SUPPORT/vms_opendir(), strcpy is being used to do an overlapping copy. Use of strcpy/strncpy for this can produce undefined results when the destination and source ranges overlap. memmove() needs to be used for these. Just found the same bug in cvt_filespec/pw6_encode(). In this case it did not seem to cause a noticable buffer overrun. And the bug is also in vms_stat/vms_stat() in two places. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
bug: vms_opendir - strcpy can not be used for overlaping moves.
In the module VMS_SUPPORT/vms_opendir(), strcpy is being used to do an overlapping copy. Use of strcpy/strncpy for this can produce undefined results when the destination and source ranges overlap. memmove() needs to be used for these. Use of strcpy/strncpy can cause a buffer overrun, which in the case I have been chasing down this afternoon, overwrote the stack when built in /NOOPT/DEBUG mode. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: bug: vms_opendir - strcpy can not be used for overlaping moves.
John E. Malmberg wrote: In the module VMS_SUPPORT/vms_opendir(), strcpy is being used to do an overlapping copy. Use of strcpy/strncpy for this can produce undefined results when the destination and source ranges overlap. memmove() needs to be used for these. Just found the same bug in cvt_filespec/pw6_encode(). In this case it did not seem to cause a noticable buffer overrun. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
bug: Infinite recursion in debug.c when debug_level = 5
There is a bug in DEBUG.C that shows up when the log level is greater than 5 and the output of SMBD is redirected to SYS$OUTPUT: What is happening is that DEBUG calls sys_fstat() calls vms_stat() which does check of the cache for /SYS$OUTPUT/smbd.log Sometimes for reasons that I do not know, the cache lookup fails, and it tries to create a new entry. This calls a hash_init routine which calls DEBUG at level 5 to log this. This starts the cycle all over again. The apparent quick fix for the debug.c is to move the save and restore of the DEBUGLEVEL value to before call to sys_fstat() and the restore to after the resulting if () block. But that also brings up some interesting questions as to why sys_fstat is going through all the extra overhead of file translation and cache processing by calling vms_stat() instead of a more simpler vms_fstat() call. Removing all that overhead should greatly improve the speed of SAMBA on VMS. I have found this while trying to merge Jean-Yves latest fixes in with the 2.2.12 source that I posted earlier. I am still chasing down a bug in the resulting 2.2.12 stream, but this bug got in the way. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba process NMBD halts the system
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: Petra Wiegmink writes: we have installed SAMBA 2.2.8 on an OpenVMS V7.3-1 system. It works alright, but within the last 10 days it happend twice that the NMBD process was using between 55 and 90% of the CPU time continuously which seriously disturbed the other processes on the system. We have stopped NMBD and started it again. It then worked alright again. Yes, I have encountered the problem, and fixed it. The fix will be available in the next release, which will be posted soon. I am waiting for a final confirmation that another problem is fixed too. Can something be done to induce these problems on demand? Can you provide more details on what the fixes are? Is this something that needs to be fixed in the mainline UNIX code? There are not many differences in the NMBD code for VMS and UNIX. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba/VMS Version 2.2.8 Build 20041021
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: I have just posted a new release that fixes some problems that happened to some of you. More information and download available, as usual, at http://www.pi-net.dyndns.org/anonymous/jyc/ Is it easy to find the changed files so that I can merge them into my 2.2.12 build? Like using the date to extract them? Also, is there any point to building on VMS 7.3-1 or later with out large file support? If not, then the DCL procedures can detect the host VMS version and make the correct changes. Otherwise a parameter such as P3 could be used to override the default. The objects proceduced by compiling on VMS 7.3-1 can not be relied on to be correct for linking on older versions of VMS unless a very complex development environment is set up, so that should not be a reason for keeping the command procedures separate. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
SAMBA 2.2.12 source kit for 8.2 (and possibly earlier)
For those interested in being more on the bleeding edge, I have now merged in the SAMBA 2.2.12 changes with last source kit that I produced. I also fixed the bug that I accidently introduced, and implemented the fsync() on the 1 byte writes to try to improve the large file issues. The source kits can be found at: http://encompasserve.org/~malmberg/samba/ SAMBA_2_2_12-V82-SRC-20041017_BCK.ZIP This has not undergone any significant testing, all I did was verify that the server will transfer some files. I have only done a test build on OpenVMS ALPHA 8.2 EFT at this time. I attempted to make this code build on older versions, but as yet I have not had time to do any test builds. Same caveats as the previous code drop. Unless something else happens, I am going to start concentrating on the SAMBA 3.x and 4.x streams. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: samba 2.2.8/time.c Question on VMS specific modification.
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: Actually, the reason is not a performance one, but the optimized Samba code does not correctly give the tm_isdst and the tm_gmtoff members of the tm struct. Now I need to find out if this is a VMS C RTL bug or a SAMBA bug, as there should not be a difference. The optimized SAMBA code is complex enough that I can not tell at a glance where the bug is actually at. Thanks. Jean-Yves, Can you set your mailer to not put a space the RE tag before the :? It should be the vendor's default setting. If the news/e-mail programs do not see RE: at the beginning of a subject line on a reply, they add one on each reply. And the news/e-mail clients/archivers also use the subject line to verify the thread context, and if they do not see that it is different only by a Re: or a RE:, they assume that this is the start of a new thread, and not the continuation of one. It is causing confusion on tracking threads in the archive and the newsgroup. Thanks, -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: samba 2.2.8/util_str.c - Why is '$' exempted from '_' replac
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: Well, basically the $ character has a special signification on Unix = which it has not in VMS. Replacing $ with _ may be useful in a number of cases, but just let's take an example where it must not be done. If you keep the default parameters for a print queue, the print command should be print %f/queue=3D%p/delete/passall. Item on the todo list is to either have a VMS specific queue module that uses the $sndjbc[w]/$getqui[w] interfaces, or provide a wrapper that presents one of the UNIX defacto standard API's like CUPS. So, now, try to create a printer share named SYS$PRINT, or try, on any printer share, to print a file named TOTO$TEXT.LOG. If you remove the '$' exemption in UTIL_SRC.C, the %f part of the command will be replaced = by TOTO_TEXT.LOG, and the queue name (%p) will be replaced by SYS_PRINT. It will not work so well... I will submit it as an enhancement to Bugzilla of a change needed in the SAMBA code specificially for VMS. Thanks, -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: samba 2.2.8/unexpected.c VMS suppressing storing of mis-dire
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: Actually, there is a reason. John Malmberg wrote: The module unexpected.c has a VMS specific change to suppress storing of mis-directed packets in the designated TDB. I don't really know why, but I have on my site quite a big number of those packets supposed to be kept temporarily in UNEXPECTED.TDB Since Dave Jones provided a new set of TDB routines, based upon RMS indexed files, such an activity of insert/delete records in that file provoked, after a few days or a few weeks, very bad performances, and high I/O activity on that file, because it became badly fragmented. To fix this, I had 2 choices: 1. Run every few days a procedure that should stop samba, convert UNEXPECTED.TDB and restart samba. 2. suppress the store/delete of the packets in UNEXPECTED.TDB It may not be the best choice, but as far as nobody here is interested in those unexpected packets anyway, and stopping/restarting samba is quite perturbing for the users, I decided to stop storing that information. I think it would have been better to add some specific VMS Global Parameter for enabling or disabling this feature, but I guess that at that time I was in some hurry, so I just disabled the storage and forgot about it since. It would seem that you made the best decision available for getting the job done on VMS. This is valuable information to know for when I start working on 3.x and 4.x. It may be that a more efficient method is needed in redirecting those packets, or even better finding out why they were misdirected. And also you seem to have observed no real problem with just dropping the misdirected packets, so I wonder what the actual impact is, or with the feature enabled, how reproducable it is. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: samba 2.2.8/util_str.c - Why is '$' exempted from '_' replac
John E. Malmberg wrote: In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: So, now, try to create a printer share named SYS$PRINT, or try, on any printer share, to print a file named TOTO$TEXT.LOG. If you remove the '$' exemption in UTIL_SRC.C, the %f part of the command will be replaced = by TOTO_TEXT.LOG, and the queue name (%p) will be replaced by SYS_PRINT. It will not work so well... I will submit it as an enhancement to Bugzilla of a change needed in the SAMBA code specificially for VMS. Bug #1916 entered in Bugzilla. Note that since the bash shell may be present on an OpenVMS system, there may be other things to consider. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Samba 2.2.8/smbd/server.c - Setting logfile directory from CLI disabled.
The module [.smbd]server.c has a VMS specific change to prevent changing the logfile directory from the SMBD command. Is there any reason that this is done? -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: smbd serves connects only when ran in interactive mode (-i)
Rabbin, Robert (GE Energy, Non GE) wrote: I have also installed the new 2.2.8 on an Alpha workstation to try to get it to work... it does everything but show up on the PC. Some more specifics may be needed: Specific version of 2.2.8? there have been several posted. Of course in this case it may not make a difference. What version of OpenVMS? What TCPIP program? Any ECOs that may be related to TCP/IP or the CRTL. It appears to be in an infinite loop until the PC times out. I have the older version running on another node in the same cluster of Alphas running v7.3 and it works instantly and reliably. I cannot upgrade until this works. Anything I should check to get it to work right? There was a discussion about this last month from someone else that was affected by this. It was started on September 11th. You can look at in the archives of this list or on the GMANE newsgroup. The discussion is fragmented into several threads because one of the mailers involved is not following internet conventions with regard to the subject line. The general thought was that it was taking too long for the TCPIP dispatcher to launch the new SMBD and for the SMBD process to complete the connection to the client. I can not find that anyone reported a successful resolution to the original poster's problem. I also have not found that all the suggested solutions were tried. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: HELP .... Documentation on installation and configuration
Usha, KL wrote: Can any one of you kindly post the documentation on installation and configuration(SMB.CONF) of Samba on OpenVMS please? The only known documentation is included in HTML format that may be readable with the SWAT program. Online documentation is also available at http://www.samba.org , but it is not taylored for OpenVMS specially. The only information is on JYC's download page, and any files that are in the distribution, and reading the archives of this mailing list/newsgroup. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
samba 2.2.8/unexpected.c VMS suppressing storing of mis-directed packets.
The module unexpected.c has a VMS specific change to suppress storing of mis-directed packets in the designated TDB. Is there any reason for this? -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
samba 2.2.8/util_str.c - Why is '$' exempted from '_' replacement?
The module [.lib]time.c has a VMS specific edit to exempt the '$' character from being replaced with an underscore. So far I can not find a reason that VMS needs this change. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: SAMBA 2.2.8 source kit for 8.2 (and possibly earlier)
Jean-Yves Collot has examined my posted changes and has discovered a bug
in the VMS_TRICKS.C
Where the old code was:
int d[2] = { 512, (int) imgname};
I replaced it with:
int d[2];
...
d[0] = 0;
d[1] = (int) imgname;
Where the interim fix would be for d[0] = 512;.
This could will disable SMBD caching and possibly introduce a memory leak.
I will not have time to address this before late tuesday evening at the
earliest, so if you are using my posted code for testing, it will need this
edit.
The proper fix would be to change d to be of struct dsc$descriptor_s and
completely fill in the descriptor values.
When VFS modules are implemented, there should not be any need for this
trick as the caching code would be contained in the VFS module, and only
the SMBD loads the VFS modules.
And I want to clarify that I am limited in what I can test, and what
VMS versions that I can build for.
I am concentrating on getting the current SAMBA releases for the 2.2.x, 3.x,
and 4.x to build on the current OpenVMS version for ALPHA and IA64, and
using only the minimum number of supplimental or replacement routines needed
for this.
The UNIX 2.2.x release is now up to 2.2.12 because of a security related
patch that was just release. That is my next target.
Since current versions of VMS support LDAP and Kerberos, I will also be
phasing in support of this in future builds, along with the HP released
version of OpenSSL. As the SSL is only for SAMBA to SAMBA connections,
it's use would be a build time option. My preference is to default it
as off.
For building and linking on older versions of VMS, I want to positively
identify exactly what suppliemental or replacement routines are needed for
them, and why they are needed. Some of the stuff in earlier SAMBA releases
was being carried around just to support versions of VMS that it was not
even possible to run that version of SAMBA on. And even now there are comments
that indicate an uncertanty of what replacement routines are needed or
not.
If there is something that needs to be enhanced or fixed in the current C
RTL for SAMBA or other UNIX program, I would like to get that formally
documented.
Compiling on newer versions of VMS and then linking on older versions is
risky and not supported by HP. Code must be compiled on the oldest
version of VMS that it will be linked against.
So if it is known at compile time that a hack/feature is not needed for
the version that is being compiled on, then the build should take advantage
of this.
There are unsupported tricks to get around this, but they involve keeping
private copies of selected files from the older VMS versions and setting
a bunch of logical names, some of which are not publically documented.
And this is not something that is easy to maintain. Especially since ECOs
also affect this.
Unless otherwise documented in the compiler documentation, redefining
a reserved predefined macro can result in undefined operation at compile
time. What you can get away with on one version/patch level of the compiler
and VMS may not apply to any other combination.
Reserved predefined macros typically start with a double underscore.
The specific rules are in the ANSI documentation and in the HP C Compiler
documentation.
So the use of the compiler pre-defined macros is to allow programs built
on a specfific version of VMS to take advantage of new features in the CRTL
or the operating system, which should make the programs more efficient.
Now if there is a strong need for LINKING on an older version of VMS than
what the modules were compile on, and no one can volunteer to compile on
that older version, then it may be possible to work out extra defines like
#ifdef VMS_TARGET_V552 to flag the hacks needed to convince the compiler
to generate the correct code.
http://encompasserve.org/~malmberg/samba/
SAMBA_2_2_8-V82-SRC-20041003_BCK.ZIP, 5504 Kb, Sun Oct 3 20:14:54 2004
Good Luck,
-John
[EMAIL PROTECTED]
Personal Opinion Only
PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:
http://www.catb.org/~esr/faqs/smart-questions.html
SAMBA 2.2.8 source kit for 8.2 (and possibly earlier)
Hello all, I have gone through the SAMBA 2.2.8 and modified it to start to take advantage of features for VMS 8.2. This also repairs most of the compiler diagnostics, including several bugfixes where the compiler would not have generated the intended code. If you are only pulling some fixes out of this, pay attention to the modules flagged with bugfix. As no one yet has complained about anything that I can trace to these bugs, I do not know how serious they are. The #ifdef ALPHA features are not #ifndef __VAX so that IA64 will use the 64 bit features. This does not have the fix that J.Y. Collot is planning for stat() returning a smaller size for a file open for write. My next step is to merge in the 2.2.12 changes, and if the bugs that I found are still present in the UNIX 2.2.12 release, to report them into BUGZILLA. I have not tested this on anything other than OpenVMS 8.2 EFT Alpha, and that was not a comprehensive test. After I get up to the 2.2.12 or what ever the UNIX release is, I may then try to build on some selected older versions. http://encompasserve.org/~malmberg/samba/ SAMBA_2_2_8-V82-SRC-20041003_BCK.ZIP, 5504 Kb, Sun Oct 3 20:14:54 2004 Good Luck, -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Archive of mailing list
In article [EMAIL PROTECTED], Plante, Sylvain [EMAIL PROTECTED] writes: Is there a specific site ( archive )where I could find all the mailing from the latest years ? http://www.samba.org, on Mozilla, on the left side is a list of links, under the heading Talk Samba. For me, the second item down is List Archives. That link will give you a number of places where SAMBA discussions are held and archived, including the gmane.org newsgroups, from which I am posting to, for those that prefer a newsgroup instead of a mailing list. Most of this information is also in the e-mail headers of every message sent from the mailing list. Some mail clinets will display this in an easy to read format. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: WinXP - OpenVMS tests reproduced using C++ test pro
Brodie, R (Richard) wrote: The stat() or fstat() functions should return the correct results of the real size of the file. In the standard fields, they should have the highest byte written in the file. The CRTL manual notes: 'be aware that for st_size to report a correct value, you need to flush both the C RTL and RMS buffers'. fflush()/ fsync() may be a mite quicker than fclose() / fopen() I suppose. Yes, and if this is backed up by the UNIX standard, means that the UNIX variants of SAMBA are possibly depending on an implementation quirk than by required behavior. Still if OpenVMS is the only one that is not behaving this way, it may be good to bring it into compliance with UNIX. -John PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: A note about HAVE_MMAP
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: Since Dave Jones provided a new, VMS-specific TDB set of routines, defining HAVE_MMAP or not has no more impact on Samba/VMS. What about the file transfer section of SAMBA where if HAVE_MMAP is set, and the smb.conf setting for it is enabled, it sometimes bypasses the stm_read() and stm_write(), and vms_lseek() routines completely and does random direct read/writes to the file on the host. This works correctly only on the STREAM and FIXed format files. For VFC files when the MMAP bypasses those routines, file corruption will appear to be present on reads, and writes can corrupt the file. It took me a while to find that in the SAMBA 2.0.6 release. There still has been no feedback to this mailing list if disabling mmap in the smb.conf file had any effect on the observed corruption of VFC files. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: A note about HAVE_MMAP
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: I don't really understand what you are referring to, but I am positive that there is not any use of HAVE_MMAP in any C file of Samba/VMS version 2.2.8. There is no any call to mmap() either, and the mmap parameter of SMB.CONF is used only for setting (or unsetting) flags when calling TDB_ routines, those flags being ignored by the new Dave Jones' specific TDB routines. The routines were present in the 2.0.x stream, but indeed, I do not find them in your 2.2.8 source code drops. So that eliminates one possibility of the data corruption for VFC files. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: WinXP - OpenVMS tests reproduced using C++ test pro
John E. Malmberg wrote: That brings up another question about the UNIX SAMBA code, since the size query is coming in on the same session that knows it has the file open, why is stat() used instead of fstat()? I would expect that fstat() would know the file highwater mark for it's current file descriptor. fstat() also is returning 0 for the test program that JYC posted. It may not be practical to get stat() changed as it is not real easy for stat() to know about what any program on the system may be doing with an open file. On the other hand, fstat() should be able to track the high water mark in the file, so maybe that can be fixed in a future release. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: WinXP - OpenVMS tests reproduced using C++ test pro
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: Hi. Now let's see the 1-byte writes and QFILE_INFOs requests. It looks like those actions are done by the client in order to provoke extensions of the allocated file space, before actually writing into it. Unfortunately, on VMS, the real size of the file is not visible until the file is closed. That can be seen by typing DIR/SIZE=ALL while the file is being written. It gives 0/. So, when the client asks for an extension (Write 1 byte) then checks the new file size (QFILE_INFO), it always gets 0 for answer. That is quite perturbing for him, so it goes on trying to extend the file. The stat() or fstat() functions should return the correct results of the real size of the file. In the standard fields, they should have the highest byte written in the file. If the file was extended with an lseek() or ftrunctate() call or just writes, then the fstat() or stat() call should reflect this. If the stat()/fstat() calls are not doing this, then a small reproducer needs to be submitted to HP so that the stat() call can be fixed. And *now* is the time to do it to make it into the real VMS 8.2 release. I made a small change on the VMS server side: when the write request is only 1 byte long, I close and reopen the file. This updates the external view of the file size. With that change, the numerous 1-byte writes and QFILE_INFOs disappear, and the dialog is exactly the same with XP client that it is with the Linux client. The time is the same too: 3.5 seconds. It would probably be better to find a way to have vms_stat()/vms_fstat() return the size that UNIX expects with out closing and reopening the file. It may take going to a vfs structure to fix that. Also did you see my note that when MMAP is enabled in the smb.conf (the default), that the stm_read() and stm_write() may sometimes be bypassed? Turning off MMAP at compile time may adversely affect the TDB code. As SAMBA 2.0.6 was before TDBs were implented, I disabled MMAP at compile time, otherwise VFC files were corrupted on some file transfers. I'll make some additional testing to check that this Close/Reopen does not have side effects, and if it does not, I'll include that change in the next release. My guess is that it should only induce a delay, but likely not as bad as what it is fixing. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Our more serious issue: two kinds of Samba read corruption
BG - Ben Armstrong wrote: - show process/acc on the user's smbd process show proc/acc/quota may provide mroe information. Accounting information: Buffered I/O count:193317 Peak working set size: 14640 Direct I/O count: 44366 Peak virtual size: 184880 What is the physical memory + pgflquo for the process? Is it equal or close to 184880? I'm thinking it might be significant that we keep our SMBD processes around for a very long time because people didn't like having to wait for their SMBD process to come into existence: deadtime = 480 Is if possible that the process ran out of virtual memory? If so, then the next step is to try to determine where the memory leak is. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: dots in directory names of shares on ODS-5 disks
Jeffrey Coffield wrote: I have a customer who wants to put dots in a directory name. Since the share is on an ODS-5 disk, this is possible for VMS but Samba 2.2.8 does not seem to follow the VMS convention of using a ^ in front of a dot. The ^ convention only applies to filenames in VMS format of DEV:[DIR]FILE.EXT. When the file is in UNIX format of /dev/dir/file.ext, no ^ should be used. Has anyone looked in to this? If not I may attempt to patch the source code. I have not looked to see if it works on SAMBA 2.2.8. So if it does not work, then yes, you may need to attempt to patch the source code. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Bug report (12=17020 TC029) SAMBA 2.2.8 release 20040908 - intermittent content loss
BG - Ben Armstrong wrote: On Fri, 2004-09-24 at 10:40 -0300, BG - Ben Armstrong wrote: I am still trying to get familiar with this code, but I am finding references to special handling if SAMBA detects that it is a VMS text file. Any VMS file that is not a stream or a fixed record size file may get corrupted by an out-of-order transfer through SAMBA as the seek() function will not go to the correct place on a write. OK, so far this is consistent with our test results. We'll let you know if we discover corruption in other file types, e.g. Stream or Stream-LF files. Oops, I misread that as seek() ... on a read, but you said on a write. Since we're seeing the corruption before any output is written, your observations are *not* consistent with our test results. So it remains a puzzle. The reason that I said on a write() is that I have only observed the segmented out of order transfer on a write. On a read, I would look for other causes. It still could be a seek() issue. It also could be that because SAMBA VMS estimated the size of the transfered data wrong, and the client believed it. My guess is that if you do not use VFC file types the problem will go away. I would recommend putting in a VMS specific bug report in Bugzilla for tracking purposes. I am planning on using that to prioritize any changes that I do once I get the build environments for SAMBA2/3/4 under control. At this time, I am looking at moving the file management into one or more VFS modules to make them simpler to maintain and debug. And then I will also need test programs to verify their operation. My suspicion is that once the corruption is properly characterized, I could probably be able to reproduce it with a small stub program that calls the VMS specific code in SAMBA, which would make it easier to debug. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba improvements needed
In article [EMAIL PROTECTED], BG - Ben Armstrong [EMAIL PROTECTED] writes: On Tue, 2004-09-21 at 08:32 -0500, John E. Malmberg wrote: And it is not preallocation that SAMBA is doing as noted below. Oh? It sure looked like it ... If you look at it from stepping through the file create sequence in the SMBD program it does. The client does tell the SAMBA server how big to make the file, but not when VMS can do it efficiently. First it has the server open the file for write access, and then it uses ftruncate() or other means to extend it. Most of these move the highwater mark of the file, unlike just allocating space. And that means that the now empty file must be totally written to disk. What's the distinction between this and preallocation? Is it that the client does the file extending writes in small increments, whereas preallocation would do it all at once? The issue is that the way that VMS is doing it now, is slightly more overhead than should be needed. First, the open/write creates an empty file. Second, the SAMBA requests that the empty file be extended to the size the client says the end file will have. This is done one of three ways, and I am not sure which method that SAMBA 2.2.8 is using. Method A, moves the high water mark and allocates the space. Method B, writes an empty file of that size. Method C ignores the request. Third, the data is written to the file. By delaying the open until there is actual data to write or the client has specified the resulting size, then Method A can be used. The other methods may show a performance hit, but this should not be reflected in the negotiated transfer protocol. It does seem that even in the WinXP - Linux case where all of the extending single-byte writes were done up front, there were way too many of them. I could well imagine that this performs poorly on OpenVMS given my (admittedly limited) understanding now of the hit we take for each preallocation. The worst run of them in my capture log started at offsets 1058815, 1059839, 1060863, etc. (i.e. 1024 byte increments) all of the way up to 2269183 before writing actual data blocks again, taking a total elapsed time of 0.94 sec. If this strategy had been used on OpenVMS, I gather the elapsed time would have been much worse. There may be a difference in a file transfered by a copy and for an application doing an open/write. Still the amount of data transferred with each packet is a function of the protocol, not the VMS file system tuning. Samba has no read. From looking at the current structure of the UNIX SAMBA code, it looks like the way to improve performance is to write VFS modules specific to ODS-2 and ODS5. The ODS5 module would not need any filename mangling. For the record, we use ODS-2, and switching to ODS-5 would be a major ordeal, as we have all of our clients to consider, not just our own systems. I understand that ODS-2 will be in use for quite a while. Supporting the Pathworks naming convention does incur significant overhead. Right now, one of the major hits for that overhead is effectively just to determine if the disk is ODS-5 or ODS-2. Getting that information requires a disk hit. Separating them into separate VFS modules will give a performance boost to directory listings for ODS-5 file systems that should be very noticable. Not being very familiar with SMB or the Samba implementation of it, I'm not sure what specific implications that has for the tests I've been performing. What do I look for in my packet capture logs to see the actual size of the file being communicated by the client to the server? That information has expired from my memory cache as it is over three years since I looked at it. And I looked at the numbers after SAMBA had extracted them from the packet, so I may never have actually seen it on the wire. And since you are using an application instead of a file copy, I do not know if the application actually knows the total size of the resulting file to send. But really, what I'm after for now is anything that might help *without* coding changes, if that is at all possible. If Richard Sharpe can find something that can be changed in the smb.conf, then it is possible. Otherwise, I suspect that a code change will be needed. Myself, I am still just getting back on this bicycle, and do not yet have my VMS 8.2 minor enhancements working. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba improvements needed
Richard Sharpe wrote: On Thu, 23 Sep 2004, John E. Malmberg wrote: However, at the time of the open request, the vfs module can take out a VMS lock on the filespec, and that will provide a cluster wide protection. ... as long as you only run Samba on one node in the cluster ... As a VMS lock is cluster wide, there should be no restriction on running it on multiple nodes. Since the tdb is disk resident on VMS, it should also be a cluster wide resourse as long as all cluster members are looking at the same tdb files. A couple of the tdb files and APIs seem to have been reimplemented using the native VMS filesystem to improve VMS's efficiency. There should not be a problem. But testing will be needed of course. Regards, -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Bug report (12=17020 TC029) SAMBA 2.2.8 release 20040908 - intermittent content loss
RR - Rod Regier wrote: (n.b. a shorter version of this was reported to JYC in August, but he was unable to reproduce the failures). Summary: Some intermittent file corruption is occuring. We would like to provide a good test case, but such eludes us. Since corruption is serious, we thought the list subscribers should be alerted to watch for same. Please take a look at the resulting file with a dir/full. I am still trying to get familiar with this code, but I am finding references to special handling if SAMBA detects that it is a VMS text file. Any VMS file that is not a stream or a fixed record size file may get corrupted by an out-of-order transfer through SAMBA as the seek() function will not go to the correct place on a write. I do not know if Samba 2.2.8 will do this, but I found some code where the VMS specific code was checking for text file types. I saw a similar problem in the SAMBA 2.0.6 timeframe that I do not recall finding a resolution to. I think it only involved VFC files that SAMBA simulates as STREAM files. I was able to reproduce the problem back then by playing with a small file originally created on VMS with notepad. My memory is a bit foggy on the details. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba 2.2.8 Print job number handling? Bug 1816
As there was no response, I have entered this into Bugzilla for tracking. https://bugzilla.samba.org/show_bug.cgi?id=1816 -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Packet analysis: WinXP vs. Linux-VMS shows dramatic differences
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: Excuse me, but I don't agree. I just ran Ben's ruby bench, which is creating that 1 Kb file, and I can see the very, very slow = behaviour: it takes more than 36 seconds to run the bench (compared to 2.35 seconds = for running a simple COPY). My error from reading too early in the morning here. I missed the Kb, and used it as bytes even though I also typed Kb The undesired behavior starts somewhere above 65535 bytes, not Kb. And it can be reproduced with a Windows NT 4.0 client on SAMBA 2.0.6. I have not tested it on anything earlier. It appears that there are two issues that affect the performance, and my guess is that the protocol negotiation is the main one. Fixing that will probably require porting a newer version of SAMBA. There are other consequences to RMS, and for the magic translation of VFC files to text files for this out-of-order translation that I want to look at also, as one of my goals is get the notepad problem on VMS fixed, even if it can not be fixed on UNIX. On VMS we have an advantage as we can tell if the file originally created on VMS is a text file, and what it's organization is. It is no problem setting up a SAMBA to serve any type of text file to a PC client as a stream-CRLF or a stream-LF regardless of it's original organization. It is handling the modify in place where the problems come in. So I think for the big problem, an updated port is needed, and for the second one, moving to a VFS loaded file system instead of wrappers for the file system calls. A VFS based system can bypass the CRTL completely to get the best speed. And by having one VFS for ODS-2 and one for ODS-5, it saves overhead on trying to support Pathworks name mangling. I also may be able to move the wild card matching into the VFS as an enhancement. I think it would speed up both the VMS and UNIX performance, especially the VMS performance. Especially with large directories. I pulled down the SAMBA4 kits last night with my barely functional rsync client. It looks like the only way to build it on VMS will initially require GNV and PERL. I do not know if I will get to trying that before next week. Regards, -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Packet analysis: WinXP vs. Linux-VMS shows dramatic differences
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: Once again, I am sorry, but it looks like I don't understand. As far as I know, Ben pointed out a problem of performances when writing files on a Samba/VMS 2.2.8 server from an XP client. I could reproduce that problem by using ruby, but I could not by using anything else. Another way to say is: according to me, the WinXP vs. Linux-VMS shows dramatic differences topic is true only when using ruby. Could someone tell me if I am right or wrong here? On SAMBA 2.0.6 VMS and Microsoft Windows NT 4.0 client several years ago, I could reproduce the same problem by just copying a large file back and forth. I used the NETSCAPE browser image for Alpha as a test case. At the time I was not trying to debug performance issues, but I did notice that the file was sent with sections out of order. When I went from VMS SAMBA to VMS SAMBA, all sections of the file were sent in the same order. What Ben has determined is that there is a difference in the protocol negotiation between SAMBA to SAMBA and Microsoft Windows to SAMBA 2.2.8. And that Microsoft Windows to SAMBA 3.0.7 is able to better negotiate the protocol. Now why SAMBA 2.2.8 on VMS is not negotiating that protocol is the unknown. As I see no VMS specific code in the sections that negotiate the protocol, I would tend to think that the answer may be in a later SAMBA release, unless there is some unknown item that is not set correctly. One test would be to try SAMBA 2.2.8 on a LINUX server and see if the same protocols are negoticated between it and the Microsoft Windows client as with SAMBA 2.2.8 on OpenVMS. If the behavior is the same on LINUX SAMBA 2.2.8 and OpenVMS, then it is likely that it will take a newer version of SAMBA to fix. If the behavior is different, then it may be able to find what needs to be changed on the OpenVMS system. Comparing the traces of the protocol negotiation with the source code of what protocols are known is another way of looking at the problem. When you refer to a Windows NT 4.0 client on SAMBA 2.0.6, or to issues dealing with modify in place stream-CRLF or stream-LF files, you are perfectly right, but I don't clearly see the connection with Ben's problem. Small connection. Ben's problem points out an issue that greatly increases the complexity of solving the conversion of stream files to VFC files. A VFC file is larger than a stream file, so it is not easy to convert it out of order. All solutions I can think of have a performance penalty, some worse than others. But that is a different problem. Porting Samba 3 or 4 to VMS is obviously a very nice thing to do, but I fear that it will take a lot of work and quite some time. In the meantime, I may be able to understand or even fix Ben's problem on 2.2.8, so I prefer to focus on that specific problem. The main advantage by working on the SAMBA3/4 port now is that it is possible to get changes put in the UNIX code that can help the VMS port, but it usually is needed to demonstrate a UNIX advantage to doing so. Once I understand all the work that you have done on 2.2.8, I do not think it will be too hard for me to get either 2.2.11. or 3.0.x running. Time however is an issue. And more volunteers that can handle implementing and testing specific issues can speed things up. I have a last question: what is exactly the notepad problem on VMS ? The notepad problem is not a VMS specific SAMBA issue, it is an issue on the UNIX SAMBA systems. It is because UNIX SAMBA serves LINUX text files as stream-LF, and Notepad wants STREAM-CRLF. Using WORDPAD or several other editors on Microsoft Windows does not show the problem, as they will auto-detect if the file is stream-LF or stream-CRLF. Most of Microsoft Windows will also handle both formats. Just like the CRTL will convert the VMS text formats to a simulated stream-LF. As it is popular to use NOTEPAD to edit text files, when those files are modified or created by the LINUX system there is a noticable problem. The part of serving the text files as STREAM-CRLF to Microsoft Windows for read only from SAMBA-VMS is easy to solve. It is the write back that is harder. If the writen blocks were always in order, than it would not be much of a problem to convert on the fly. With the written blocks out of order, the insertion of the out-of-order blocks will result in having to move some of the earlier written blocks to make room, something that is not good. Tempfiles can not be used as the server does not know if this is a file transfer, or an application doing random read/write access to a file. Now the last time I did any research on this was at least three years ago, so I may be a little fuzzy on the details. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
AAD has broken challenge response system
If anyone posting is not getting the AAD challenges, can you let them know that their challenge response system is badly broken, and needs to be configured to never challenge posts to mailing lists that their users have subscribed to. Neither answering the challenges or sending notes to their role accounts seems to be fixing this problem. From what I have seen of challenge response systems that do not use SMTP transaction codes, they seem to be the best way to make sure that important e-mail does not get delivered. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Samba improvements needed (was: WinXP-Linux samba server test)
In article [EMAIL PROTECTED], BG - Ben Armstrong [EMAIL PROTECTED] writes: On Mon, 2004-09-20 at 18:32 -0400, John E. Malmberg wrote: What version of SAMBA is running on the LINUX system? Samba 3.0.7 + smbfs 3.0.7. Other than that, I am not set up to take advantage of your data at the moment. I do not have any way of reading the etherreal data. If it is because you don't have a Linux system, the ethereal data is not specific to ethereal or Linux. A number of utilities can read it, some of which run on OpenVMS, and many of which run on Windows. Tcpdump, which is available for TCPIP 5.4, can read it. For example: $ tcpdump==$sys$system:tcpip$tcpdump $ tcpdump -vr test.cap I do not have a LINUX system running at this time. Three years in my new house, and I have not had time to organize that section of the basement to get one of now ancient 100Mhz/90 Mhz sytems wired up to the LAN let alone running LINUX. Also, tcptrace, which, like tcpdump, is based on libpcap, can read it. See: http://jarok.cs.ohiou.edu/software/tcptrace/download.html That may be useful, once I get 2.2.11 or 3.0.7 or the SAMBA4 to build and run, if the problem still remains. I find it rather interesting that Linux can negotiate Write AndX to write large buffers at a time to OpenVMS, and Windows can negotiate Write AndX to write large buffers at a time to Linux, but Windows can only negotiate Write to write 1K blocks at a time to OpenVMS. It may be a difference between Samba 2.2.8 and later versions. Also, if pre-allocation is an expensive operation in OpenVMS, doesn't that indicate there is room for improvement here in the current Samba implementation for OpenVMS? That is very much an understatement. Volunteers are needed for an almost unlimited number of tasks, some big, some small. And it is not preallocation that SAMBA is doing as noted below. Since the Windows host insists on preallocating, and since OpenVMS Samba refuses (or is unable) to send back EOF and allocation responses to the file info requests, it appears that Windows thinks it can only pre-allocate a small amount ahead of where it is writing, instead of further ahead, as it does in the Windows - Linux case. Wouldn't sending back EOF and allocation figures allow the Windows client to write further ahead, resulting in fewer preallocation requests? As it stands, after the first 64K are written, one file info + one extra preallocation write are done per 1024 byte block written! That is exorbitantly expensive, and totally unnecessary, if only the server would give the client the info necessary to make larger, and therefore fewer preallocation writes. The client does tell the SAMBA server how big to make the file, but not when VMS can do it efficiently. First it has the server open the file for write access, and then it uses ftruncate() or other means to extend it. Most of these move the highwater mark of the file, unlike just allocating space. And that means that the now empty file must be totally written to disk. From looking at the current structure of the UNIX SAMBA code, it looks like the way to improve performance is to write VFS modules specific to ODS-2 and ODS5. The ODS5 module would not need any filename mangling. In that module, when a open +write access is done to create a new file, the VFS would delay actually opening the file until either the first data is actualy written, or the client (as per usual observed practice), sends down the actual size of the file. More buffering may also help. The VFS approach may allow more efficient application cache management and tuning. As it is, I am trying to do what I can. J.Y.C. Has done a tremendous amount of work with the 2.2.8 port, and I am trying to understand what changes that he made and why, and if any of the issues that I posted to this list before his port appeared have been resolved. At this point I am trying to optimize the 2.2.8 port for the new features found in OpenVMS 8.2 EFT, while still making it build and work on older versions as a secondary feature. Then I will look at doing a quick merge of the 2.2.11 Samba version. I am also trying to get involved with the SAMBA4 project, as they seem to have some buildable code. That way I may be able to find a way to get some changes in the code that can help VMS performance, especially if I can show them to help UNIX performance to. I have not yet been able to scope out a complete TODO list. At a minimum, current versions of VMS include LDAP and Kerberos, but the VMS Samba builds do not use them. SSL is also available as an option to VMS. The documentation package DOCBOOK?, rsync, subversion, need ports. I am working on rsync also, and have a almost functional client. CUPS and SYSLOG replacement libraries would probably help. Test suites need to be written, especially for the wrapper functions. The setuser.mar needs to be replaced with Persona Services for the applicable versions of VMS
Re: RE : RE : smbd serves connects only when ran in interactive mode (-i)
Ashot Bord wrote: JY, thanks for trying it out! I ran it on SIMH, the simulator. It is not speedy for CPU, but fast with IO. It may as well be that the CPU speed is the cause of the broken socket, but FTP in service mode doesn't have any sensible delays and doesn't time-out, and it also spawns a child. I still suspect there could be some sockets issue, possibly related to TCPIP itself. I read of other users running SAMBA on SIMH, though not sure about their VMS/TCPIP config. Try installing the SMBD.EXE image as /SHARED/HEADER resident. This will both speed up the image activation time, and will also reduce the physical/virtual memory requirements of running SAMBA. IIRC: There is some code in SAMBA 2.0.6 that calculates a machine SID on startup, and since VMS does not support the preferred routines, the fall back is not very efficient. I have not checked that section of the 2.2.8 port yet to see if has that issue. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Samba 2.2.8 Print job number handling?
Is there code in the SAMBA 2.2.8 port to deal with mapping the VMS job number to a range that will work for SAMBA? The VMS job number is an unsigned 32 bit integer, and the SMB protocol can only handle a 16 bit integer. So there needs to be a dynamic mapping of VMS job numbers to SMB job numbers. Or ever time a job number larger than 65535 is issued, it will not be accessible to SAMBA. For 2.0.6. I set the job name to encode the SMB job number, so that the print queue management commands would work only with print jobs submitted through SAMBA, as that was the only ones that the translation could be verified. If this still is an issue with SAMBA 2.2.8, I will enter a bug in BUGZILLA to track this. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: WinXP-Linux samba server test results
BG - Ben Armstrong wrote: Hi, Here is an analysis of my next test, supplemental to my earlier observations about WinXP - OpenVMS samba write performance. If you want to skip the details and cut to the chase, it seems that both when WinXP talks to a Linux samba server and when Linux talks to a OpenVMS server, efficiencies of the SMB protocol are being taken advantage of that are missing in the WinXP to OpenVMS server conversation. I am supplying my further analysis below in case it helps resolve this mystery, and particularly in case it helps us tune our server and/or clients to perform optimally. What version of SAMBA is running on the LINUX system? Other than that, I am not set up to take advantage of your data at the moment. I do not have any way of reading the etherreal data. It may be useful if you can find a specific difference in the protocol negotiation if the SAMBA versions are the same. -John [EMAIL PROTECTED] Personal Opinion Only AAD- If you are seeing this, your Challenge-Response system is badly broken and is probably discarding a lot of mail. It should never be challenging mailing list e-mails. PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Windows-VMS Samba performance issue
In article [EMAIL PROTECTED], BG - Ben Armstrong [EMAIL PROTECTED] writes: We have observed that a Linux 2.6 client using smbfs completes a simple write large files benchmark of our own devising* 10 times faster than a Windows client on the same network with the same load! This suggests that there is great room for improvement just by changing some settings -- possibly some of the socket options, as a casual review of the Samba literature suggests. VMS version? TCPIP platform and version? Samba version? Any work in that area would be appreciated. Also if you can run the torture tests against the SAMBA 2.2.8 to indicate any functionality that is not working properly. The tests supplied with the SAMBA kit do not seem to have been ported to OpenVMS. There are a number of tuning issues that I addressed in a SAMBA VMS FAQ, of which the latest copy I did is available from a GOOGLE search, even though it is quite old. In general, some of the socket options may help. What I would expect to make the biggest difference is setting the RMS default buffer sizes. There is one key difference in how some Microsoft Windows clients treat large files and how SAMBA does. SAMBA sends the file sequentially from start to finish. For some unknown reason, Microsoft Windows sends the first part of the file, skips a bit and sends the middle, and then backfills. This may affect how OpenVMS is handling performance. And it just may be a case where SAMBA to SAMBA transfers are more efficient than WINDOWS to SAMBA transfers, since you would expect that if it were really a server issue, that the server would perform badly for both clients. If you use a LINUX SAMBA server instead of a VMS SAMBA server, do you see the same difference in performance? The SMBD.EXE image needs to be installed as shared to reduce the virtual memory load and to speed up the startup of new instances. This is not likely to help the large file transfer much, but it is a related to do option. So what we're after now is some pointers for tuning so that we can realize with a Windows client a similar level of performance to the Linux client. We need to know how to find out which settings are out of whack, and how to choose from among the thousands of possible knobs we could fiddle with. General VMS tuning should be looked at. Make sure that WSMAX / WSEXTENT is large enough to keep processes from paging excessively. The RMS buffering mentioned above. You also will want to make sure that your non-page pool is adequate. With your normal steady state load, the usual recomendation is that there should be 300,000 bytes free, with out any pool expansion having taken place. Or were you looking for Windows client tuning tips? -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
External Authentication? (WAS: http://www.samba.org links to )
In article [EMAIL PROTECTED], [EMAIL PROTECTED] writes: John, If you have time, can you add the ability to have SAMBA operate as a VMS password provider (aka Pathworks) that can update the VMS password from a Windows Domain? I may look at it down the road a bit. Actually, I do not think that Pathworks updates the VMS password from the Microsoft domain. It sends the password to the domain controller and accepts the result. It may then update the VMS password for use in case the domain controller is down, but I do not know about that. I think that the required acme$ interfaces are now publically documented. I do not have a system running that can be a domain controller at this time for testing though. For people interested on working on this, the procedure should be: 1. Get password from the user. 2. Send password to the domain controller for authentication. 3. Generate a local VMS hash for the password, and update the sysuaf for that user if different. 4. Update the local SMBPASSWD file with the NT and lanman passwords if needed. The SMBPASSWD program needs to be installed with privilege so that the SMB PASSWORD file can be protected with NO access to non-privileged users. The SMBCLIENT program should be modified to use the SMB PASSWORD file as a PROXY database so that the user does not have to enter their password, or track it separately as an environmental variable. That will also require it to be installed with privilege enough to read the SMB PASSWORD file. That makes it easy to set up a print queue to print to a LANMAN printer with the username of the logged in user. At the present time, I will likely be doing only fine-tuning and not much in the way of inovation. And from what I have learned in the past week, I need to get a build environment using logical name search lists, and .MMS scripts, otherwise it is too long on my hardware to make test builds, and too easy to mess something up. I also need to set up a todo list. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
http://www.samba.org links to VMS port being updated.
Hello Jean-Yves, I requested that the main SAMBA team reference your page as the current SAMBA-VMS port, and they agreed to do so. That change should take effect in the next 24 hours to all the mirrors. Thanks for all the good work, I am starting to look at the 2.2.11, 3.x, and 4.x versions. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: New Samba/VMS Release : build 20040908
In article [EMAIL PROTECTED],
COLLOT Jean-Yves [EMAIL PROTECTED] writes:
Now, the news.
Good, I will pull down the new kit immediately.
I am trying to find out two things.
1. I can not get guest access to work.
2. When I turn up the debugging level, the server takes too long and the
client times out. I am also not seeing anything in the debug messages
from the server about it trying to access the guest account.
1. A new VMS Record Format share parameter has been added. It defines the
RMS record type of the files created by Samba, i.e. the way VMS will see
those files. The default is stream, but it can be forced to stream_lf.
I hope that it's decision is based on a file extension. SAMBA 2.0.6 had
this feature, but it was global by file extension, not by share type.
The main reason for this is that SAMBA 2.0.6 was trying to make sure that text
files looked correctly on either the client or the server, regardless of the
original format. I never fully achieved that goal.
2.0.6 used the format of a previous generation of a file to determine
the record type on creation, but if no previous generation existed, it
would look in the template directory for a file with that extension, and
use that instead.
7. The code has been checked in order to remove the /STANDARD=VAXC compiler
option in COMPILE.COM, and to remove irrelevant warnings and informations.
However, depending upon the version of the DECC compiler you use, you may
encounter a lot of informational messages if you choose to recompile
Samba/VMS from the sources. You may prefer to use the old procedure, which
is now included under the name COMPILE_STD_VAXC.COM
When you did this check, did you fix the bug in blocking.c that the
compiler flags if you have the /warn=enable=(level4,questcode) set?
In the old code, since blr-expire_time is of unsigned type time_t, this
expression will never be true, so locks can never expire.
This appears to be a bug in the UNIX distribution for any compiler were
time_t is unsigned.
As of yet, I do not know the impact of this bug on the VMS platform.
$ diff [-.smbd]blocking.c/ignore=trail
File PROJECT_ROOT:[SAMBA-2_2_8-SRC.SOURCE.SMBD]BLOCKING.C;3
644 if((blr-expire_time != (time_t)-1) (blr-expire_time = t)) {
645 /*
**
File PROJECT_ROOT:[SAMBA-2_2_8-SRC.SOURCE.SMBD]BLOCKING.C;2
644 if((blr-expire_time != -1) (blr-expire_time = t)) {
645 /*
Adding the following to config.h should remove most of the noise for
a current C compiler.
/* Disable noise about compiler extensions */
/*=*/
#pragma message disable pragma
#pragma message disable hexoctunsign
#pragma message disable valuepres
#pragma message disable intconcastsgn /* Commonly assumed correct */
#pragma message disable questcompare2 /* Commonly assumed correct */
I have not yet inspected all the questcompare2 warnings to verify that
they are indeed nothing to be concerned about.
I have still not completed a build with that warning level as I am adjusting
the code to use either a 64 bit or 48 bit ino_t, and fixing all the minor
informationals except those messages above.
Also most of the #ifdef __ALPHA need to be change to #ifndef __VAX,
otherwise the IA64 binaries will be built wrong.
There is also a problem in the includes.h where two needed include files
are not included before proto.h. In this case the C compiler will do
the correct code even though diagnostics are generated.
#include nsswitch/sys_nss.h /* needed by proto.h */
#include nsswitch/winbindd_nss.h /* needed by proto.h */
Also, with 8.2, a number of new features and fixes are expected to be in
the CRTL, including a standards compliant stat()/fstat() and statvfs(),
including handling the dev_t type the way SAMBA expects.
The [.vms]grp.h, pwd.h, and utime.h supplied should only be needed
prior to 7.3.
Regards,
-John
[EMAIL PROTECTED]
Personal Opinion Only
PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:
http://www.catb.org/~esr/faqs/smart-questions.html
Re: RE : New Samba/VMS Release : build 20040908
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: Hi. 1. I can not get guest access to work. I think it works here, but may be I am not doing what you want to do. What I do is : - define SAMBA__GUEST as the guest account in SMB.CONF - define Bad user for the map to guest parameter (Never is the default) Here was the problem. In 2.0.6 it may have been a compile time option. Over 3 years, and I am getting forgetful. The documentation on it is correct and incorrect depending on how you look at things. It states that the map to guest only affects access to services that are not shares. That is not exactly true, but not exactly false. If you have map to guest set to never, you can access guest shares from WINDOWS-95 and earlier with out supplying a username and password. You can not from Windows NT 4.0 and later. The reason is that they request a list of services from the server, and that requires either the map to guest account to be bad user, or it requires that the user supply a password to the account they are using. So thank you for that fix. And it looks like I need to supply a document enhancement request to the UNIX samba team. And it works. In addition, if I define 2 as log level, I have no timeout problem, and I get messages in the log such as : connect to service share1 as user samba__guest (for guest ok = Yes shares) Invalid username/password for share2 [samba__guest] (for guest ok = No shares) I was trying between 4 and 8 as log level. With SAMBA 2.0.6, I could usually run at least a level 8 on smbd with out any timeouts, and that was even with the output being directed to a terminal emulator. I hope that it's decision is based on a file extension (about the VMS Record Format parameter) Actually, I added that feature because Mr Tapani Rundgren ([EMAIL PROTECTED]) asked for it. Mr Rundgren is using a software product that writes files on Samba/VMS shares, but separates the written lines by LF instead of CRLF. This is the case, for example, if you use smbmount from a Linux box, and create text files with vi or any Linux tool. When a VMS program or procedure tries to read such files, it does not see any line terminator, and sees the files as if they have only one big line. The parameter gives the opportunity of telling VMS that the line terminator is a single LF. This is a parameter attached to the entire share (a similar option exists in Pathworks). I was taking a different approach to solving that and a greater problem. Samba needs to present the variable length text files from OpenVMS as streamCRLF for notepad to be able to read them. And then if notepad modifies the file, it needs to be written in the same format it originally was in. So for known text files, I was converting them on the fly so that a PC would see them as streamcrlf, and VMS would see them in the format that the user desired. But other files should be treated as either stream files or binary files. Some of it had to do with making sure that true RMS record locking would work well. I did not take the time to figure out how to make it share specific, which is definitely preferable to making it global to the server. But it is do able, and the code in my 2.0.6 almost works. I ran out of time to figure out the last part. The problem is with large files, greater than 128Kb in size, and only shows up in transfers from Microsoft Windows to a SAMBA server. It never shows up with a transfer from SAMBA server to SAMBA client. This is because SAMBA always transfers the file in order. Microsoft Windows does not, for the large file I was testing, SAMBA transfered about the first 32K bytes, then skipped 32K bytes of the file, and then transfered some middle parts of the file, and then went back and filled in the parts that were skipped. For binary files, no problem. For a text file opened in record mode, it gets totally corrupted, as there is no way to know how many records were in the section that was skipped. But I did not want to have to convert files from VMS text format to one of the stream formats before putting them on a SAMBA share. I don't understand what you mean by basing the feature on a file extension. In my example (Samba share accessed thru Linux smbmount, and accessed thru some Windows box at the same time), a text file will have only LF when created from Linux, but will have CRLF when created from Windows. I think that you can't securely assume that a given file comes from Linux because, for example, its extension is .lis, or from Windows because its extension is .txt And when created from VMS will have a variable format, which is natively unreadable to either LINUX or Microsoft Windows, unless SAMBA translates the file contents one way or another. As you say, there is no way to make an assumption, so I made it configurable by the server administrator with the default to do no conversion. -John [EMAIL PROTECTED] Personal Opinion Only
RE: We are pleased to hear of your support for OpenVMS on
In article [EMAIL PROTECTED], Tillman, Brian (AGRE) [EMAIL PROTECTED] writes: Michael A. Fitzgerald ([EMAIL PROTECTED]) wrote: Dear Samba, Dear Samba?? Perhaps someone shouldn't be using a form letter. Apparently this is a result of Sue Skonetski publicizing Robert Thomas's post here about getting SAMBA to run on OpenVMS 8.1. I have forwarded that note to some people in HP. I do not see a problem with the note being posted here though. It would seem that if someone wanted to sell consulting support for SAMBA on VMS including IPF, they would be interested in participating in this program. The attachment was missing because the mailing list strips all but a small number of attachment types. Samba seems to run on OpenVMS 8.2 internal releases also, but I have not done any real testing on it. There is a bug in the IA64 C compiler on VMS that prevents one of the modules from compiling that Robert mentioned in his report. The workaround is to compile that module/OPT=INLINE=NONE In order to use the cross compiler, I had to change the COMPILE.COM procedure to not change the symbol definitions for CC and link. $ ccflags :=/DECC/noLIST/INCLUDE=- ([],[.INCLUDE],[.UBIQX],[.SMBWRAPPER],[.tdb],[.popt],[.VMS]) - /STANDARD=VAXC/NESTED=PRIMARY/nowarning /PREFIX=ALL - /DEFINE=(WITH_SMBPASSWD_SAM, HAVE_IFACE_IFCONF)/name=SHORTENED $ compile_mains: $! $ ! SRV_SPOOLSS_NT Hack $ if p2.eqs. .or. p2.eqs.SRV_SPOOLSS_NT $ then $ filename = SRV_SPOOLSS_NT $ dirname = RPC_SERVER $ Write sys$output Compiling ''filename' in ''dirname' $ CC'ccflags'/OPT=INLINE=NONE [.'dirname']'filename'.c- /OBJ=[.'dirname']'filename'.OBJ $ LIBRARY/REPLACE [.bin]samba.OLB [.'dirname']'filename'.OBJ $ delete [.'dirname']'filename'.OBJ;* $ endif -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: RE : SAMBA 2.2.8 misc issues.
In article [EMAIL PROTECTED], COLLOT Jean-Yves [EMAIL PROTECTED] writes: 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. It is not really a GUEST account, it is the account that is used for the security credentials for all remote IPC communications which need to access the local file system, in addition to what is used for GUEST access to shares. Which is why it must be a dedicated account that does not have write access to anything other than it's home directory, and the samba_root:[var] directory. It is a manditory feature of the LANMAN protocol to have such an account. It is really mis-named in it's function. When you disable the Guest account on a real Windows box, you in reality are only disabling it for use with connecting to the file and print shares. The Guest account is still used for other purposes. Samba does not currently have a way to follow that model, except to mark the shares in smb.conf as not accessable by the GUEST account. For SAMBA on VMS to have the GUEST account behave the same way as on Windows, it would have to pay attention to the SYSUAF DISUSER flag if it was being used to access a file or print share. In SAMBA 2.0.6, that could be done through an easy change in the Frontport wrapper library. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: RE : Link problems with V2.2.8
Leo Klein wrote: $ @link Linking SMBD %LINK-W-NUDFSYMS, 2 undefined symbols: %LINK-I-UDFSYM, DECC$GXSNPRINTF %LINK-I-UDFSYM, DECC$GXVSNPRINTF Several of the newer xxxSNPRINTF variants are not in the older CRTL and are being added to the newer versions. For older CRTLs, you must supply replacement routines. When supplying the replacement routine for a standard C library, it must not have the same public symbol name as the routines, as this will cause problems. Some of these problems will be visible at link time, some will not, and may take quite a bit of effort to find why the code is malfunctioning. The GXSNPRINTF and GXVSNPRINTF calls can be generated by the compiler for a variety of public C RTL routines depending on your optimization settings, so you have to look at the source modules. It should not be hard to write replacement routines, and likely they are already present in the SAMBA code, and a change to config.h will make them active. For example, a missing VSNPRINTF routine would be replaced with a routine named rep_vsnprintf, or samba_vsnprintf, or my_vsnprintf. In the config.h there would be an option: #define HAVE_VSNPRINTF or #undef HAVE_VSNPRINTF Depending on if your platform supports that call. In one of the header files, or in the modules that use vsnprintf(), there would be the following conditional code, or something similar. #ifndef HAVE_VSNPRINTF #define vsnprinf samba_vsnprinf #endif If you need to supply your own replacement routine, then the above conditional code would be put in the CONFIG.H file to minimize edits to the common UNIX SAMBA code. And even though it seems to be an easy thing to do, do not ever name the replacement routine the same as a standard C library function. A good optimizing C complier knows about many of the library routines and will in line them, so if you are trying to change the behavior of a standard function, the compiler may not realize that, and inline the standard function. Also the link time substitution of user supplied routines covering up system libraries only works reliably on platforms that do not use shared images for their libraries. People who do not heed the above warning usually end up with others that try to build their code posting on comp.os.vms trying to find out why they are getting weird build errors after an OpenVMS upgrade or C RTL ECO. Anything that is using standard C function names for their own public symbols is virtually guaranteed to eventually not build on OpenVMS. And several people have posted on the SAMBA Technical list for various UNIX platforms that have the same problem when SAMBA did the same thing. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Windows Change Password
Michael Ober wrote: I need to be able to change the password on our VAX system from the Windows password change dialog. Is this possible with Samba VMS. I'm running Samba Version 2.2.8 on HP TCP/IP Services for OpenVMS Alpha Version V5.4 on a AlphaServer 1200 5/533 4MB running OpenVMS V7.3-2. Setting Samba to authenticate against the domain is insufficient as my users also need to login to the VMS system directly. The Microsoft UNIX Compatibility package for Windows NT 4.0 came with source code for a utility that could intercept a password change dialog on a PC client, and then relay the results to a UNIX system. A privileged daemon on UNIX would then set the password there. It should be adaptable to SAMBA and OpenVMS. IIRC: The Microsoft APIs for intercepting the password change are documented in their MSDN and TECHNET dialogs. Another HACK that may be more risky is to set the selected VAX accounts not to have a password, and in SYLOGIN.COM to use SMBPASSWD to validate the login. Of course this must be done only for terminal class logins interactive logins. To do this, you must modify SYLOGIN that if a NETWORK class login comes in from a source that you do not have a proxy for, it will be denied. [And you will quickly find all the command files with usernames and passwords coded in them] And since those VMS accounts will not have passwords, you must set Samba to authenticate against the domains. There are risks of doing this in that you may not cover all the login cases. So I would recommend studying things carefully before implementing this second method. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: 2 GB limit?
COLLOT Jean-Yves wrote: I started to have a look on this 2GB size limit, and I don't clearly understand the last couple of messages in this list, about the _LARGEFILE definition. I suppose that you make references to some SAMBA/VMS version older than the one (2.2.8) on which I am working. _LARGEFILE is a macro definition that you can put in the CONFIG.H and in the OpenVMS wrapper code on V7.3-1 and later to get 64 bit file sizes. I do not know if the support in V7.3-1 or V7.3-2 is good enough to fully support Samba. In addition for those of you that are playing with using RMS to suppliment the stat() routines, on an ODS-5 volume, RMS can return the number of actual data bytes in the file instead of just the size. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: SMBMOUNT
Stephen Eickhoff wrote: Is there anyone currently working on getting SMBMOUNT support in the VMS port? Probably not. It would require an executive or kernel mode interface into the TCP/IP stack on the system, and that is not documented at this time. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Mapping Windows 2000 Drives/Shares from VMS
Matthew Robey wrote: Hi, I am running VMS V7.3-1 with TCPIP V5.3 eco 2 and Samba V2.2.8 Is it possible to map a Windows 2000 drive/share from VMS ? I can list the shares by doing: $ smbc -L windows server -U username But I cant work out how to use it to 'map' a drive. You can not map a drive on OpenVMS. It would require implementing a SMB file ACP on OpenVMS, and that would be a lot of work, and probably require the source listings. With out an assist from some TCP/IP internals, it also probably would be extremely slow. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: This message is in MIME Format
Rachel Wrote: [Message is currently being held in the possible spam queue for manual release. I do not have authority to release it] X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary=_=_NextPart_001_01C3DC2F.91D69A40 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --_=_NextPart_001_01C3DC2F.91D69A40 Content-Type: text/plain; charset=iso-8859-1 Good Day I have the following error. Kindly let me know how to resolve it This message is in MIME format since your Mail reader does not understand this information some or all of this message may not be legible. Is this problem coming from the server (Exchange 5.5) or from the clients machines? Regards, Rachel Rachel, you will see that error message when someone sends a MIME formatted e-mail to a mail reader that either does not understand MIME, or has MIME disabled for security reasons. E-Mail traditionally is PLAIN-TEXT only. MIME is an optional enhancement that should only be used when you know that the recipiant wants to receive it. The SAMBA mailing lists will remove all but the plain text portions of a posting, and any attachements that are not plain-text. This can leave message like that in posting, particularly when spam gets through. The MIME part of the spam will not get through. Your message was sent in MIME, and that may be reasont that the SAMBA spam filter flagged it as possible spam for manual moderation. I would recommend that you set your e-mail program to send in plain-text by default when mailing out to the public internet, and only turn on HTML or RICH TEXT when you are sending to someone that you know wants to accept MIME formatted e-mails. This will help prevent content filters from misclassifying your e-mail. Almost all spam or viruses are sent in HTML format, so the presence of the HTML and the tag that your mailer put on the message are one of the key metrics that a content based spam filter looks for. Some people will go so far as to automatically delete unread all MIME encoded e-mails. In addition, if your e-mail program is displaying HTML by default, and opening external links for pictures automatically, it can give out information to spammers automatically. When an e-mail program opens a link in the spam, it uses your web browser program to do so. That link at a minimum tells the spammer that your mail server is accepting their spam, so that they can target more spam to your domain. The link can also have your e-mail address encoded in it, which confirms to the spammer that your e-mail address is live and that their spam is getting through to it. In addtion some web browsers will happily give out your e-mail address to web sites that ask for it. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Please do not quote spam to the list.
Gibberish? AI test? Or Al Queda communique? You decide! Spam. The MIME filter removed the advertisement for pills like that have been laboratory tested to contain fecal matter and insect parts and other apparently inert matter. All that was left is the hash buster that fooled the content filter. Please do not quote spam to a mailing list. The SAMBA lists use a bayesian filter to identify spam, and when anyone quotes a spam post that gets through, it makes it harder for the filter to detect similar spams as it negates the spam score from the spam analyzed. This is also the case for individual bayesian filters. Thank you, -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba/VMS 2.2.8 New version available
COLLOT Jean-Yves wrote: A new version is available on http://www.pi-net.dyndns.org/anonymous/jyc/ It fixes a couple of problems and includes Dave Jones's enhancements for the readline routine Please submit it to the OpenVMS freeware maintainer. It may still be able to make it into the next release. http://www.hp.com/go/openvms, and follow the freeware link. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: startup help
Hank Vander Waal wrote: I am trying to startup samba ver 2.2 on an open vms system. I have the samba process running on VMS side but I can not see the samba box when I brose the network from my win2k system. What basics am I missing ? There should be file named Diagnosis.txt or equivalent that describes how to use NSLOOKUP and SMBCLIENT to troubleshoot your Samba Server. That said, the symptom looks a lot like not having a SAMBA_GUEST account that can read and write to it's login directory and to SAMBA_ROOT:[VAR]. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Samba 2.2.8 on VMS 7.3-1
Geoff Roberts wrote: Still having difficulty making Samba useable. As above. To an XP box. No domains involved. It now asks for username/password but never authenticates for some reason. (SMB is set to use encrypted p/w and XP does so by default). The username must exist on the OpenVMS system, and have both read and write access to it's default directory, and to SAMBA_ROOT:[VAR]. The password is validated against the Samba password file or a remote server. But the UIC used comes from the OpenVMS account. Also, the SAMBA_GUEST account must exist, and it must have read and write access to it's default directory and to SAMBA_ROOT:[VAR]. Because of the unique security requirements, I strongly recommend that a special account SAMBA__GUEST be used. The SAMBA_GUEST account is misnamed. It is not really a guest account, and is required for most clients to do any access to the server. When you disable the Guest account on a Microsoft Server, it is not totally disabling the account. Certain network operations still use the security information from that account according to people who work on the main SAMBA core. Also could someone point me to some *VMS Specific* docs. The online html docs are useful but are rather too unix specific for someone that doesn't speak Unix. For Samba 2.0.6 and earlier, I put a FAQ on comp.os.vms and in Encompasserve. http://www.google.com should be able to find it. A couple of people on comp.os.vms have expressed an interest in writing up a more OpenVMS friendly how-to or quick start for SAMBA, but I have not seen any documentation. Nor have I seen them post on this mailing list. The comp.os.vms newsgroup is an alternate place for asking about SAMBA for OpenVMS. Also as SAMBA for OpenVMS is more closely tracking the behavior of the UNIX SAMBA, sometimes an answer can be found in the main SAMBA mailing list. Be warned, that one has a higher volume. (Like me). Is there some UID equivalent that needs to be poked in somewhere in addition to username and hashed password? Is there some way to make it use the SYSUAF instead of a separate user database? As I posted above. Samba on OpenVMS uses the SYSUAF for two accounts for every connection. To get it to just use the SYSUAF, you need to disable encrypted passwords. Other changes may be required. I'll post my smb.conf or anything else that might help. Posting the entire smb.conf or other large logs rarely helps. Increasing the debug level and then looking at the last few lines of the resulting smbd log in SAMBA_ROOT:[VAR] will usually show what the problem is. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Not really out of disk space problem (was Re: deafening silence...)
Tim Oakley wrote: Hi, Since i posted a problem last friday, the silence has been deafening. Has no one else encountered the problem i described ? I saw reports of it intermittantly a long time ago with a Microsoft NT Server. I include the text of my original message below: best regards ** I have a perplexing problem which i will try to explain simply I was running Samba2.2.7a (2nd release) on a vms7.2-2 machine. Everything worked fine. I updated the server to vms7.3-1 and installed the 'vms731_update_v1' 'vms731_rms_v4' eco's. I reinstalled Samba2.2.7a on the updated system to ensure the 'link.com' would use the newly installed RTLs. All was OK except for one user (USER1) whose pc app no longer worked. The app basically takes a text file from a samba share and sends it down a modem line to an automated banking service. The app failed saying that there was insufficient space on the samba share drive, which was not true. I think the app tries to create a temporary file on the samba share. I have not worked directly with SAMBA for a while, but sometimes such problems are caused by applications seeing more than 2 GB free, or some number like that. A temporary workaround for that problem is to put a big file on the share so that the free space appears smaller, until an updated application is available. To further diagnose this problem would either require a packet sniffer trace or a debug log, and if it is not obvious from that, would require some assistance from someone familiar with the code. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Mail Admin: SAMBA-VMS list is being flooded.
Martin Pool wrote: Hi John, This block is now in place. Let me know if trouble persists. Thanks, I have had one response from one of the Austrailan virus scanners claiming that they have fixed their virus scanner. For urgent issues like this it is better to write directly to postmaster at samba.org -- I for one read that more frequently than s-t. Ok, I will try to remember that. I see that a old? virus claiming to be [EMAIL PROTECTED] and has attempted to deliver three copies to the samba-vms list members. Source: 65.96.38.72 - Comcast.net. I would be surprised if anyone on the open-vms mailing list would object to it being restricted to subscribers. I am switching to using the newsgroups that mirror the Samba lists, as it is much more convenient for reading. Thanks, -John PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: virus warning
Stephen Eickhoff wrote: Please block this nuisance! I think that it is under control now. I posted a request last night in the samba-technical group to block them. I also suggested that it may be time to require subscription to the mailing list to post. I also have been sending manual notifications to the networks who have the misconfigured to send these useless notifications. If you go to the samba.org web pages for the mail server, it will give you instructions on how to use a newsreader to access the samba lists so that you do not have to get them by e-mail. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Installing Samba on VMS 7.3-1 using Multinet 4.4a
Nails, Dana wrote: I have been trying to configure Samba for days on our Alpha system. What we are wanting to do is store print files on our alpha and be able to view them through Word, Notepad, etc using Samba. We have an NT Domain. Every user has a domain account and an alpha account. I have been able to set up a share and see the share but I can not look or browse the files. Any suggestions to fix this problem. I do not recall seeing any response to this here, which is rare. The newsgroup comp.os.vms may also be of assistance. In the SAMBA distribution there used to be a Diagnostics.txt file with a list of things to test. There is also an FAQ that I posted to comp.os.vms and encompasserve.org last January. It does not cover the 2.0.3, but it does cover a number of items. http://www.google.com. In general the DOS net view, the SAMBA NMBLOOKUP, and SMBCLIENT should be used to verify connectivity. Increasing the DEBUG level on the SMBD process can sometimes show what the problem is. I have not actually done anything with SAMBA with about a year. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
RE: Samba Documentation
On Wed, 2 Jul 2003, Boyce, Nick wrote: Paul, 1) Your symptom description came through to me as : This works sometimes, but then I get ...OLE_Obj... I guess your OLE_Obj didn't make it through our firewall. Please either (a) attach it as a (small please !) graphic image file, or (b) just tell us what the error message was in text. None of the SAMBA mailing lists will accept most attachments by intention. They also remove the HTML portion of posts. Paste inline with plain text, and then it will get through. Also if you did not note it, please specify the date of the .ZIP file that you downloaded SAMBA from as all the 2.2.x.? downloads use the same filename. The version of SAMBA, and the version of OpenVMS, the version of TCP/IP and any CRTL ECO kits are usually also needed. There may also be methods of telling SAMBA what type of file structure to use depending on the version that you are uisng. -John [EMAIL PROTECTED] Personal Opinion Only [Internet access impaired this week] PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Problems using Samba/VMS Print shares
Dave Jones wrote: I'm gradually working on a fresh port of 2.2.8, most recently working on a VMS native printer interface. All the print queue operations are done by way of SYS$SNDJBC and SYS$GETQUI calls rather than spawning DCL commands. It's fairly self-contained, so I put the sources in a zip file at http://www.er6.eng.ohio-state.edu/~jonesd/samba/print_vms_1.zip Just out of curiosity, how are you mapping the either 8 or 16 bit NT job entry numbers that the client needs to track to the 32 bit entry numbers generated by OpenVMS? I can not remember from the last time I looked at this issue if NT job numbers were 8 bit or 16 bits. Also, if you are doing a fresh port, it may be better to start with the 3.X version of SAMBA. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
RE : Problem with VMS_SUPPORT.C
COLLOT Jean-Yves wrote: John Malmberg wrote: These open/writes should not update the file modification dates. The only way I see around this is to track to see if the file was actually modified and then use the XQP function to restore the dates to what they were when the file was opened. I completely agree. That's exactly what the last Samba/VMS version does. Unfortunately this is the wrong thing to do when their are multiple users accessing the file. If one of them modifies the file on purpose, that modification date gets lost. Either pure RMS or ACP calls need to be used, or an extension is needed for the C RTL. The extension would be to allow XABs to be added on to a file open request. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
RE : Problem with VMS_SUPPORT.C
B. Z. Ledermman wrote: DISK$STORAGE:[SAMBA-2_2_7A-SRC.SOURCE.VMS]VMS_SUPPORT.C;262:(394) vms_statfs: $GETDVI ERROR for disk$lederman^:^[lederman^].: sts= 0144, iosb = 0144 The error is in what ever routine is converting UNIX filenames to VMS. It is setting the : as a filename character, and not as a device delimiter. And unless the SAMBA panic handler has been disabled, calling LIB$SIGNAL on fatal errors can really lead to some interesting and useless tracebacks. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: Compiling SAMBA with better options
From: B. Z. Lederman wrote: I've been looking more at the source code and the way it's compiled. /STANDARD=VAXC is really not a good choice. It covers up too many real and potential problems in the code. Use /STANDARD=PORTABLE. Do not use /STANDARD=VAXC Use /WARN=ENABLE=(LEVEL4, QUESTCODE) for the diagnostic level. You can use more strict /STANDARD or /warn and other checking if you wish, but the two settings above are the minimum needed to both find common bugs, and to be compatable with common programming practices. If the /warn=enable=(LEVEL4, QUESTCODE) and /STANDARD=PORTABLE does not compile a UNIX samba module, try it again by adding /ACCEPT=NOVAXC If that does not fix it, then update the source and send a explanation of the bug fix allong with a submit a gdiff -u output of the change to the SAMBA-TECHNICAL list so it can be fixed in the source for all platforms. If you have not submitted patches to the SAMBA-TECHNICAL list before, I recommend posting just the lines that you think needing fixing both old and new to this list for review. Please be brief. There is also a question of what to do with names that are longer than 31 characters. I put #define statements in the config.h or equivalent. Having the names truncated will cause duplicate symbol errors in SAMBA. The only thing that I can find in the standard is that only 8 characters for external names are guaranteed to be available on all platforms, and obviously most code needs more than that. The other option is to allow the compiler to mangle names. I prefer not to do that as then I can not always predict what name will show up in the debugger. Particularly if the demangle database is cleared. [SAMBA-2_2_7A-SRC.SOURCE.SMBD] CLOSE.C because it calls sys$open, sys$close, etc. without the functions being defined. Modules that call these functions are better off if they #include starlet.h to define the function prototypes. There are a couple of other modules where this should be done. I personally find that the #include files for the system service modules to not be accurate because they do not use the const modifier where they should and they tend to use void *, which will accept anything with out a complaint. So I usually prototype the system services manually, like I did in Frontport. That way the compiler is more likely to find bugs. The use of the const modifier on variables passed by address also allows the compiler to optimize more effienciently, which means faster and smaller code. It's use should be greatly encouraged. An unknown person wrote: (post is not in the digest) | I quite agree with your remarks, but I fear that you seem to forget a very | important point : Samba/VMS is a port from a quite complicated software that | comes from Unix, and is quite often updated. If you multiply the #ifdef | for VMS specifics, you begin to have a lot of work each time a new release | comes in, if you want to follow the Unix updates. So I tend to limit the VMS | specific changes to truly functional ones, not for the intellectual benefit | of removing warning or informational messages. That is why I did the SAMBA 2.0.6 port the way I did. Amost no #ifdef __VMS is in the code. Carl Perkins has supplied me with a fix to Frontport that probably eliminates all but one of the #ifdef __VMS. Use of the compiler options that I listed earlier should allows SAMBA to compile unless there is a real bug in the source code. I add a /DEFINE=(MOD_modulename) to the MMS C compiler rule so that I can put things that are specific to a module in the config.h or equivalent. That way I can override a local routine with out having to edit any source code. The MMS definition is below, and it is easy to do this with DCL command procedures. MODN =MOD_'f$element(0,-,f$parse($*,,,NAME))' So in the config.h or equivalent, (Since I am now generating the config.h from a command procedure that knows how to read the config.h.in and configure.in files, and search the DECC images and libraries, I now put all the manual edits in config_vms.h) #ifdef MOD_LOADPARM /* Change the name for a VMS specific wrapper */ /**/ #define lp_load samba_lp_load #endif This allows me to scan the VMS specific SAMBA logical names every time that SAMBA scans the smb.conf file for changes. And if a module informational diagnostics that I do not want to submit a fix for, I can supress those on a per module basis. #ifdef MOD_IPC /* suppress messages about using -1 as third arg to SSVALS() macro */ #pragma message disable intconstsign #endif This is a case where they are using a -1 instead of 0xFFF. The problem with fixing this is that the size of an unsigned int is platform specific, so it really should be ~0 instead. However if I remember correclty that also generates a diagnostic. So I just supress the diagnostic for now. An unknown person wrote: (post is not in
Please do not send out-of-office reports to postings.
Folks, If you are using and out-of-office or vacation notice program on your e-mail program, please set it so that it does not respond to mailing list e-mails. There should be a setting for this, as mailing list e-mails have special codes in their headers to identify them. Contact your e-mail administrator if you need help on this. Also be aware that at least one convicted criminal has stated in interviews that he and others use out-of-office notices from e-mail and voice mail to locate targets for identity theft. This method was used to steal from many companies before this person was caught and is still being used by other criminals. So sending an out-of-office message to unknown people is not a good idea for your personal or company security. A voicemail message can give an alternate contact, but should not let out information to a criminal to know that you are not going to be around for a while. On a U.S.network TV show a few years back, it was demonstrated to a company by a security specialist that just by using a phone and calling until they got an out-of-office voice mail they were able to obtain the dial in number to the computer network, and got an account name from the help desk and the password reset. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
Re: RE : stat (AGAIN!)
[bcc to:] Jean-François PIÉRONNE wrote: Then I found that there was a PYTHON version of Rsync, but that the Python port was not operational. Jean-Francois Pieronne has remedied that for the most part, but I am trying to make things better with it's build. I hope to be testing pysnc soon. Well, I tend to disagree, Python port is operational, It is now, thanks to you. But I was refering to the what was left on the web before you started posting the kits again. So we are not in dissagreement, perhaps a language difference. the only known problems are on non-blocking mode socket and into the sprintf port (VMS don't provide snprintf) which appear to not correctly format some big number. The snprintf is coming, and the compiler knows how to optimize it. It already is having problems because the of the name conflict with the internal routine and the external routine. So far these problems are not directly visible. A replacement routine for a broken or missing official UNIX function should not have the same symbol name. This causes problems on OpenVMS and some UNIX platforms. The better the optimizer in the compiler, and the better that the platform manages virtual memory, the more likely you are to encounter it. So replacement routine for foobar() from a UNIX library should be replaced with my_foobar(). And then the following macro should be used in the config.h or equivalent to make sure that the rest of the code finds it like below. #ifndef HAVE_FOOBAR #ifdef foobar #undef foobar #endif #define foobar my_foobar #endif If foobar takes a fixed number of arguments, a macro that specifies them is preferred. This prevents problems if someone decided to name a structure or structure member the same name as a function. #define foobar(a, b, c) my_foobar(a, b, c) If you do not do this, an optimizing compiler will use it's internal knowlege of a routine instead of calling the replacement routine, or you may get a duplicate symbol at link time. The perl port just tripped over this with the last ECO to the C runtime library. But the current port is based on 2.3 which is still under development. Python pysync and rsync.py work but it seem that they don't include the server part, only the client part. I have test locally these two tools successfully. Good to hear that they worked locally. The next step is to see if they can be used to keep a local copy of a master open-source library up to date. -John [EMAIL PROTECTED] Personal Opinion Only PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
