I never tried to use Samba on a volume-set, but I can understand why you
encounter the behaviour you describe.
In order to be aware of changes (file creations/deletions), Samba uses the
internal locks maintained by the file system (XQP). Because those locks are
not the same for volume sets, it
Hi.
I must admit that I don't clearly understand myself what is the use of some
parameters in the SMB.CONF file.
However, after having checked the code, I can say the following:
1. create mask and create mode are synonyms, so if you put both
parameters in the SMB.CONF file, only the last one
I remember that those failed to change delete on close flag errors where
linked to a more general problem of file interlocks and sharing, which was
fixed with the 20050201 version. There was no changes in this area since.
I suggest to check that the .TDB files situated in the
, you wrote:
At 01:53 PM 8/17/2005 +0200, COLLOT Jean-Yves wrote:
A new version (20050817) is available at
http://www.pi-net.dyndns.org/anonymous/jyc/
JYC
-Message d'origine-
De : Rodney Kimber [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 17 août 2005 01:57
À : COLLOT Jean-Yves; samba-vms
A new version (20050817) is available at
http://www.pi-net.dyndns.org/anonymous/jyc/
JYC
-Message d'origine-
De : Rodney Kimber [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 17 août 2005 01:57
À : COLLOT Jean-Yves; samba-vms@lists.samba.org
Objet : RE: RE : Samba 2.2.8 (JYC 31-Mar-05
Hi.
I don't have this problem here (or I don't do what must be done to see it).
What would be the right values for total size/free space on your system ?
How do you get the wrong values (Explorer/Properties or by other means) ?
JY
-Message d'origine-
De : [EMAIL PROTECTED]
It is true that the VMS modification is changed when the file is opened in
read/write mode, even if the file is not actually written. In fact, the
modification date is changed when the file is closed.
In order to fix that, in version 2.2.8, Samba keeps track if the file is
really changed (i.e.
The current VMS/Swat version and distribution kit changes xxx.n.html to
xxx.n_html.
In the next distribution, I will change that in order to replace xxx.n.html
by xxx_n.html.
I know that this is not enough, and that the html files must be modified
too, but I hope that this change will be a
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.
JY Collot
PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:
Hi.
If the problem happens again, it would be most interesting to know if the
files were actually NOT deleted, or if they were, but they seem to stay
anyway because their names remained in the cache.
The best way to know that, obviously, is to check on the VMS side if the
file is there or not.
Actually, what Rod said is not exactly true. It depends if the VMS disk is
ODS-2 or ODS-5. Both cases give bad results, but not the same ones.
On ODS-2, both NEXT. and NEXT.DIR are seen as directories. We see two
directories with the same name, Next. The result is that it's impossible
to do
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.
If some of you need to have the fix sooner,
You are perfectly right about this DEBUG bug.
However, in the 2.2.8 code, sys_fstat actually calls vms_fstat. It is
vms_fstat which is redirecting that call to vms_stat, causing the questions
you ask. I am the guilty one for this.
Actually, I had a couple of reasons for doing this, even if they
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.
JY
-Message d'origine-
De : Petra Wiegmink [mailto:[EMAIL PROTECTED]
Envoyé : jeudi 21
]
Envoyé : jeudi 21 octobre 2004 18:13
À : [EMAIL PROTECTED]
Objet : 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
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.
The localtime call is not quite expensive on VMS, so I preferred to use
the standard DECC version, which is correctly working.
JY
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
For this one, there is no reason I can remember.
In addition of not having any reason, this is clearly a bug. If you use the
-l option, you just don't get any log.smbd file !!! I guess (and hope)
that this option is rarely used.
Sorry about that. I'll remove that specific change.
JY
Can you set your mailer to not put a space the RE tag before the :?
It should be the vendor's default setting.
I understand the problem, but I really don't know how to do that. My mailer
is Outlook 2002 SP2, and I wandered through most of the menus without
finding where I can change it.
If
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.
I am not sure it should. Anyway, it does not and, as far as I know, it never
did in DECC or VAXC RTL history.
If
Since Dave Jones provided a new, VMS-specific TDB set of routines, defining
HAVE_MMAP or not has no more impact on Samba/VMS.
JYC
PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:
http://www.catb.org/~esr/faqs/smart-questions.html
This will be fixed in the next release. Note that dots in a directory name
will only be available on ODS-5 disks.
Jean-Yves Collot
-Message d'origine-
De : Jeffrey Coffield [mailto:[EMAIL PROTECTED]
Envoyé : samedi 25 septembre 2004 13:56
À : 'Samba VMS'
Objet : dots in directory names
Hi.
After some research, I have answers about that issue.
Actually, when analysing the network dialogues between the Samba/VMS server
and the clients, there are two differences:
1. The block size (1024 bytes when XP client, 61 Kbytes when Linux client)
2. The 1-byte writes and QFILE_INFOs
Hi.
I was very interested (and very surprised) by the experiments and results
described in the last messages, so I tried to reproduce the issue myself.
Note that, instead of using Ethereal or other utilities, you can run smbd
with log level 3, and all the transactions are logged.
I downloaded
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
The point is that, according to the logs, there is more than 6 seconds
between the first line of the log (Samba starts) and the error message (
socket not connected). I could reproduce the same socket not connected
error by adding a 5 sec sleep in the Samba code.
Services such as FTP do not have
This would indicate that something in SWAT is doing a translation.
Yes, sure, something does. A piece of VMS-specific code in CGI.C keeps only
the first dot(.) and replaces all subsequent dots by underscores(_). After
that, I renamed the files (i.e. SMBD.8.HTML to SMBD.8_HTML).
JY
PLEASE READ
Well, this is quite surprising.
Could you give me some more information ?
1. The results of $ TCPIP SHOW SERVICE/FULL SMBD
2. A copy of your SMB.CONF file
3. Set the log level to 3, delete SAMBA_ROOT:[VAR]LOG.*;*, retry to access
a share from your PC, and please send me the full files LOG.SMBD
A couple of other questions :
- What is the BYTLM quota of the user associated with the TCPIP SMBD Service
?
- what is the value of the SYSGEN parameters PQL_MBYTLM ?
- Can you correctly use SWAT from the PC or not ?
(i.e. http://your-server:901)
JY
-Message d'origine-
De :
Is there anything in the LOG.SMBD and/or LOG.your-pc files in the
SAMBA_ROOT:[VAR] area ?
What is the log level in SMB.CONF ?
JYC
PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:
http://www.catb.org/~esr/faqs/smart-questions.html
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)
- define guest ok as Yes in some shares,
As you see, with this release I start a new policy of naming the kit files.
I hope it will satisfy those of you who asked for an easiest way of managing
the Samba/VMS versions.
The kits will now be named SAMBA-2_2_8-specific-buildnumber.zip, where :
- specific can be :
o OBJ: Objects
I posted on the download site (http://www.pi-net.dyndns.org/anonymous/jyc/)
the file containing the missing modules, and some explanation about using
it, for those of you who use old VMS versions.
JYC
-Message d'origine-
De : Leo Klein [mailto:[EMAIL PROTECTED]
Envoyé : samedi 19 juin
Michael Lemke wrote :
Well, for what it's worth, I had the same problem a while ago. I solved
it by rebuilding from source and modifying config.h or whatever that was
until all the unsupported *printf routines wheren't needed.
Yes, this is a good solution, if you have the DECC compiler
No, you can't ignore those link messages. Samba won't work.
Please download from HP and install the latest available CRTL patch kit for
your VMS version, and it should be OK to link and run Samba.
JY
-Message d'origine-
De : Leo Klein [mailto:[EMAIL PROTECTED]
Envoyé : mardi 15 juin
I posted on the usual http://www.pi-net.dyndns.org/anonymous/jyc/ location a
new couple of kits that supports big files (i.e. files bigger than 2
Gigabytes). Except this feature, there is no differences between this kit
and the standard one, so if your files are not so big, you have no reason to
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.
Having made a couple of tests,
I don't. In my opinion, it is far too much complicated to achieve,
considering the time I can spend on it.
JY Collot
-Message d'origine-
De : Stephen Eickhoff [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 10 mars 2004 03:45
À : [EMAIL PROTECTED]
Objet : SMBMOUNT
Is there anyone currently
Actually, as you may guess, the bad performance is due to the number of
files in a directory (in fact, the size of the directory (.DIR) file), not
of the size of the files themselves. Because of the RMS directory caching
feature, the real gap is when the directory file is bigger than 127 blocks.
Sure, it works well. The SWAT program is implemented as a TCP/IP service on
port 901, so if the SWAT service is enabled, you just have to connect to it
on http://your-node:901
JY
-Message d'origine-
De : Hank Vander Waal [mailto:[EMAIL PROTECTED]
Envoyé : mardi 27 janvier 2004 03:02
À :
This is an issue already fixed in the last Samba/VMS version
-Message d'origine-
De : Terrence Branscombe [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 12 novembre 2003 03:32
À : [EMAIL PROTECTED]
Objet : Curious lock problem
PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:
Hi.
That's my fault. For performance reasons, I changed the default Samba/VMS
option for oplocks to No.
I must admit I don't clearly understand what those oplocks are and what they
are supposed to do. I just saw that when enabled, they add activity of IP
messages between the smbd processes on
The problem here is that, for performance reasons, some kernel locks are
used by the SMBD process, and those locks are created when calling stat().
Unfortunately, stat() is called by other Samba components (such as
smbpasswd), and it takes (or tries to take) the same kernel locks, even if
there
Your TDB changes will be included in my next version.
Thanks.
PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:
http://www.catb.org/~esr/faqs/smart-questions.html
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
Why shouldn't Samba handle files in the same way that most FTP
servers on VMS do: use RMS to read the records and push them
to the client?
It's basically what Samba does, but, for the moment, only when the
variable-record file is opened in Read-only mode, and this single test was
OK when
Connections is one that I would want to move to use the LOCKING code.
Connections must be removed from the table if a SMBD process crashed.
Removal of old connections from crashed SMBD processes is now done : when a
new connection comes in, all connections in the TDB file that is owned by
non
Hi.
Could you give me a copy of the full line (or lines) of the log where the
error appears ? It should look like $GETDVI ERROR for xxx: sts = nnn,
iosb=yyy
You are right that GETDVIW should be better than GETDVI, but this is clearly
not the point. In addition, you CAN use a full file spec for
The 2.2.8 version for VMS is available at
http://www.pi-net.dyndns.org/anonymous/jyc/
It includes the Unix version 2.2.8, and some specific VMS fixes :
- Unexpected changes of file structure (VARIABLE to STREAM) and modification
date
- Correct display of the file dates (no more differences
Doing whatever F11X$POSIX_FASTRDSEQNOS does. This is one of
two things - it either enqueues a lock and dequeues the lock
(...) , or it directly accesses the memory structures used by the
lock manager
The routine actually enqueues/dequeues a lock, and does not access directly
the lock
Using your method instead of opendir() readdir() seems very interesting, and
will certainly give better performances. When your version of VMS_OPENDIR
works, I'll be happy to put it in the distribution.
Please check that it works too with ODS-5 file system, with the extended
file names !
For
Without knowing what is using the internal routine, I do
not know if it will remain, will be removed, or if changes to RMS will
leave it totally or partially non-functional.
Actually, this internal routine uses a feature of the XQP, not of RMS, but
it's a detail.
It may work for now, but as it
We have many filenames with double underscores ( __ ) under VMS and they
do not appear under Windows explorer.
I have a look on Internet it seem to be normal under Samba Vms !!!
The best idea I have is to use ODS-5 file system on your disk.
Another way is to define the logical name :
$
(about F11X$POSIX_FASTRDSEQNOS) :
I am trying to find out how stable that internal routine is. I am
trying to see if a supported interface can be developed to either give
notification on change, or a way to detect changes in the directory.
As did Dave Jones (thanks again to him), I looked
Dave is right : i twas not correct.
I'll correct that for the next release. You'll have to wait a little
longer...
JY
PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING:
http://www.catb.org/~esr/faqs/smart-questions.html
SAMBA 2.0.6 allows the smbd process to be run interactively
Sure, 2.2.7 kept that very interesting feature for debugging. The syntax is
RUN SAMBA_ROOT:[BIN]SMBD -i -dn
n being the debug (trace) level you want. Between 3 and 5 is usually enough
to have a lot of information.
Before
That's just great. Does not seem to work on VAX platforms, however.
I'll include that in the new release.
Thanks a lot
JY Collot
-Message d'origine-
De : Dave Jones [mailto:[EMAIL PROTECTED]
Envoyé : lundi 3 mars 2003 07:57
À : [EMAIL PROTECTED]
Objet : Detecting directory changes.
I
That will be corrected in the next release.
-Message d'origine-
De : Fezay Georges [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 26 février 2003 12:02
À : '[EMAIL PROTECTED]'
Objet : Samba/Vms 2.2.7a
Hello,
I have installed Samba/Vms 2.2.7a with OpenVMS V7.2-1 and TCPIP V5.0A on an
Title: Samba/VMS 2.2.7a performances
Hi.
I am almost ready to give a new release of Samba 2.2.7a. It will be available later this week, or at least at the beginning of next week.
The main change is that I completely re-wrote the TDB stuff (processing of the files who keep information
Title: RE : SAMBA v2.2.7a issues
Hi everyone.
First, thanks for your thanks, and keep updated for the next release, which will be available within a couple of weeks, I hope, because it will be better...
For the 1st question (Unknown socket option), I am sorry, but I did not remove from
Title: RE : Problem file lookup on 2.2.7a Alpha
Hi.
Well, you are perfectly right, and it actually is an issue... For performance reasons, I try to cache data in memory (directory contents and file characteristics), and only go back to actually reading the disk only when needed.
The
Title: RE : RE : Problem file lookup on 2.2.7a Alpha
No, as far as I know.
-Message d'origine-
De : Michael D. Ober [mailto:[EMAIL PROTECTED]]
Envoyé : lundi 24 février 2003 17:52
À : 'COLLOT Jean-Yves'; '[EMAIL PROTECTED]'
Cc : [EMAIL PROTECTED]
Objet : RE: RE : Problem file
Title: RE : Samba/Vms 2.2.7a ODS-5 support
Sorry about that, sometimes my guesses are wrong...
However, you should test this problem with the new version, because I don't encounter it myself.
JY
-Message d'origine-
De : Carl Perkins [mailto:[EMAIL PROTECTED]]
Envoyé : jeudi 23
Title: RE : Samba/Vms 2.2.7a ODS-5 support
Yes.
-Message d'origine-
De : Michael D. Ober [mailto:[EMAIL PROTECTED]]
Envoyé : jeudi 23 janvier 2003 15:33
À : Samba VMS
Objet : RE: Samba/Vms 2.2.7a ODS-5 support
Does this version also fix the Win98 name mangling issue?
QUOTE
From
64 matches
Mail list logo
