Discussion:
evfsgui-20-GA-20091224.wpi
Doug Bissett
2010-01-09 23:52:32 UTC
Permalink
I am experimenting with SAMBA and EVFS. The results are rather mixed.
On a newly installed eCS 2.0 Silver system, both samba-1-0-3.wpi and
evfsgui-20-GA-20091224.wpi installed, with no trouble, and appear to
be working (but eVFS seems to have a problem - more below).

Since I am not, yet, prepared to commit to SAMBA, I left NETBIOS over
TCP/IP installed on my main system (eCS 2.0 Silver), and just instaled
EVFS. The install appeared to go successfuly, but when I attmpted to
start EVFSGUI, the program appered in the eCenter (LSwitcher), but the
window didn't open, and one processor was at 99%. I also tried EVFS on
an older eCS 1.2 system. Same symptoms (using the older WinList in
eCenter, and only one processor). I was able to kill the program with
CADH, in both cases. After a while, I realized that neither of those
systems were loading the driver:
IFS=M:\ECS\BOOT\EVFS.IFS
RUN=M:\ECS\BIN\EVFSCTL.EXE

I am not sure why that was not in the Silver system, but it wasn't.
After installing that stuff, it started to work. Perhaps it would be
good for the WarpIn installer to determine if that driver is
installed, and warn a user that it is required, if it is not. It would
also be good if the program itself would warn that the driver is not
running, rather than just hanging.

Okay, I got all of that to work. Now, I discovered another rather
serious problem. I have one directory that has 302 files in it, served
by NETBIOS over TCP/IP. When I attempt to display the contents, using
EVFS (the resulting drive object), that directory only shows about 88
files. The other systems show roughly the same number of files (93,
and 98), but not the whole thing. Using a command line against the
drive shows the same as the drive object (even on the same system, but
the real directory shows them all). Using the requester from NETBIOS
over TCP/IP, shows all of the files.

Am I missing something, or is EVFS dropping data, with no warning?

I also like the new "Network Neighborhood", in EVFSGUI, but that does
sound rather windowish :-) Perhaps it could be named something more
appropriate, like "Network Roadmap". I find that on one system that
refreshes almost immediately, but on the other three systems, it takes
up to 20 minutes for the icon tree to show up. I can use the Dialog
before the icons appear.

Samba seems to be working well, but I can't use it exclusively, until
the missing files problem is resolved.

Thanks...
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Pete Brown
2010-01-10 02:29:55 UTC
Permalink
Hi Doug
Post by Doug Bissett
I am experimenting with SAMBA and EVFS. The results are rather mixed.
On a newly installed eCS 2.0 Silver system, both samba-1-0-3.wpi and
evfsgui-20-GA-20091224.wpi installed, with no trouble, and appear to
be working (but eVFS seems to have a problem - more below).
Since I am not, yet, prepared to commit to SAMBA, I left NETBIOS over
TCP/IP installed on my main system (eCS 2.0 Silver), and just instaled
EVFS. The install appeared to go successfuly, but when I attmpted to
start EVFSGUI, the program appered in the eCenter (LSwitcher), but the
window didn't open, and one processor was at 99%. I also tried EVFS on
an older eCS 1.2 system. Same symptoms (using the older WinList in
eCenter, and only one processor). I was able to kill the program with
CADH, in both cases. After a while, I realized that neither of those
IFS=M:\ECS\BOOT\EVFS.IFS
RUN=M:\ECS\BIN\EVFSCTL.EXE
I am not sure why that was not in the Silver system, but it wasn't.
After installing that stuff, it started to work. Perhaps it would be
good for the WarpIn installer to determine if that driver is
installed, and warn a user that it is required, if it is not. It would
also be good if the program itself would warn that the driver is not
running, rather than just hanging.
Okay, I got all of that to work. Now, I discovered another rather
serious problem. I have one directory that has 302 files in it, served
by NETBIOS over TCP/IP. When I attempt to display the contents, using
EVFS (the resulting drive object), that directory only shows about 88
files. The other systems show roughly the same number of files (93,
and 98), but not the whole thing. Using a command line against the
drive shows the same as the drive object (even on the same system, but
the real directory shows them all). Using the requester from NETBIOS
over TCP/IP, shows all of the files.
Am I missing something, or is EVFS dropping data, with no warning?
No, that is the same behaviour I reported a little while back.

I think it may be something to do with smb/cifs differences between
samba and OS/2 NETBIOS (Peer).

The probable cure is to remove NETBIOS and install samba server but I
have not got to the stage of trying that yet.
Post by Doug Bissett
I also like the new "Network Neighborhood", in EVFSGUI, but that does
sound rather windowish :-) Perhaps it could be named something more
appropriate, like "Network Roadmap". I find that on one system that
refreshes almost immediately, but on the other three systems, it takes
up to 20 minutes for the icon tree to show up. I can use the Dialog
before the icons appear.
Up to 20 minutes? - well, I never waited that long before deciding there
was some sort of problem.

Interestingly it seems to revolve around the fact that Windows has a
"master browser" competition and OS/2 NETBIOS does not. You can test
that by having a win system running on the network - the refresh is
instant then.
Post by Doug Bissett
Samba seems to be working well, but I can't use it exclusively, until
the missing files problem is resolved.
As mentioned above the only current answer seems to be using samba
server instead of OS/2 NETBIOS.
Post by Doug Bissett
Thanks...
Have fun :-)

Pete
Doug Bissett
2010-01-10 16:27:12 UTC
Permalink
On Sun, 10 Jan 2010 02:29:55 UTC, Pete Brown
Post by Pete Brown
Hi Doug
Post by Doug Bissett
I am experimenting with SAMBA and EVFS. The results are rather mixed.
On a newly installed eCS 2.0 Silver system, both samba-1-0-3.wpi and
evfsgui-20-GA-20091224.wpi installed, with no trouble, and appear to
be working (but eVFS seems to have a problem - more below).
Since I am not, yet, prepared to commit to SAMBA, I left NETBIOS over
TCP/IP installed on my main system (eCS 2.0 Silver), and just instaled
EVFS. The install appeared to go successfuly, but when I attmpted to
start EVFSGUI, the program appered in the eCenter (LSwitcher), but the
window didn't open, and one processor was at 99%. I also tried EVFS on
an older eCS 1.2 system. Same symptoms (using the older WinList in
eCenter, and only one processor). I was able to kill the program with
CADH, in both cases. After a while, I realized that neither of those
IFS=M:\ECS\BOOT\EVFS.IFS
RUN=M:\ECS\BIN\EVFSCTL.EXE
I am not sure why that was not in the Silver system, but it wasn't.
After installing that stuff, it started to work. Perhaps it would be
good for the WarpIn installer to determine if that driver is
installed, and warn a user that it is required, if it is not. It would
also be good if the program itself would warn that the driver is not
running, rather than just hanging.
Okay, I got all of that to work. Now, I discovered another rather
serious problem. I have one directory that has 302 files in it, served
by NETBIOS over TCP/IP. When I attempt to display the contents, using
EVFS (the resulting drive object), that directory only shows about 88
files. The other systems show roughly the same number of files (93,
and 98), but not the whole thing. Using a command line against the
drive shows the same as the drive object (even on the same system, but
the real directory shows them all). Using the requester from NETBIOS
over TCP/IP, shows all of the files.
Am I missing something, or is EVFS dropping data, with no warning?
No, that is the same behaviour I reported a little while back.
I think it may be something to do with smb/cifs differences between
samba and OS/2 NETBIOS (Peer).
The probable cure is to remove NETBIOS and install samba server but I
have not got to the stage of trying that yet.
Post by Doug Bissett
I also like the new "Network Neighborhood", in EVFSGUI, but that does
sound rather windowish :-) Perhaps it could be named something more
appropriate, like "Network Roadmap". I find that on one system that
refreshes almost immediately, but on the other three systems, it takes
up to 20 minutes for the icon tree to show up. I can use the Dialog
before the icons appear.
Up to 20 minutes? - well, I never waited that long before deciding there
was some sort of problem.
I was able to use theDialog to connect, so I left it run for a while.
After I came back, the tree was there. After that it worked fine,
until I closed EVFSGUI, and opened it again, then it took another 10
minutes to populate.
Post by Pete Brown
Interestingly it seems to revolve around the fact that Windows has a
"master browser" competition and OS/2 NETBIOS does not. You can test
that by having a win system running on the network - the refresh is
instant then.
No, that doesn't seem to have anything to do with it. I see the same
thing with XP running on one of the systems, and it does appear that
my router takes on that roll when there is no windows system present.
The odd thing is, that the one system with both SAMBA server, and
EVFS, refreshes almost immediately, every time, while the other system
with SAMBA server, and EVFS, takes a long time to refresh. I need to
do more experimenting to see if I can establish a pattern to what is
going on.
Post by Pete Brown
Post by Doug Bissett
Samba seems to be working well, but I can't use it exclusively, until
the missing files problem is resolved.
As mentioned above the only current answer seems to be using samba
server instead of OS/2 NETBIOS.
I will try that.
Post by Pete Brown
Post by Doug Bissett
Thanks...
Have fun :-)
It is always fun, but plese let me know if you find a source of 48
hour days :-)
Post by Pete Brown
Pete
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Pete Brown
2010-01-11 14:54:04 UTC
Permalink
Hi Doug
Post by Doug Bissett
On Sun, 10 Jan 2010 02:29:55 UTC, Pete Brown
Post by Pete Brown
Hi Doug
Post by Doug Bissett
I am experimenting with SAMBA and EVFS. The results are rather mixed.
On a newly installed eCS 2.0 Silver system, both samba-1-0-3.wpi and
evfsgui-20-GA-20091224.wpi installed, with no trouble, and appear to
be working (but eVFS seems to have a problem - more below).
Since I am not, yet, prepared to commit to SAMBA, I left NETBIOS over
TCP/IP installed on my main system (eCS 2.0 Silver), and just instaled
EVFS. The install appeared to go successfuly, but when I attmpted to
start EVFSGUI, the program appered in the eCenter (LSwitcher), but the
window didn't open, and one processor was at 99%. I also tried EVFS on
an older eCS 1.2 system. Same symptoms (using the older WinList in
eCenter, and only one processor). I was able to kill the program with
CADH, in both cases. After a while, I realized that neither of those
IFS=M:\ECS\BOOT\EVFS.IFS
RUN=M:\ECS\BIN\EVFSCTL.EXE
I am not sure why that was not in the Silver system, but it wasn't.
After installing that stuff, it started to work. Perhaps it would be
good for the WarpIn installer to determine if that driver is
installed, and warn a user that it is required, if it is not. It would
also be good if the program itself would warn that the driver is not
running, rather than just hanging.
Okay, I got all of that to work. Now, I discovered another rather
serious problem. I have one directory that has 302 files in it, served
by NETBIOS over TCP/IP. When I attempt to display the contents, using
EVFS (the resulting drive object), that directory only shows about 88
files. The other systems show roughly the same number of files (93,
and 98), but not the whole thing. Using a command line against the
drive shows the same as the drive object (even on the same system, but
the real directory shows them all). Using the requester from NETBIOS
over TCP/IP, shows all of the files.
Am I missing something, or is EVFS dropping data, with no warning?
No, that is the same behaviour I reported a little while back.
I think it may be something to do with smb/cifs differences between
samba and OS/2 NETBIOS (Peer).
The probable cure is to remove NETBIOS and install samba server but I
have not got to the stage of trying that yet.
Post by Doug Bissett
I also like the new "Network Neighborhood", in EVFSGUI, but that does
sound rather windowish :-) Perhaps it could be named something more
appropriate, like "Network Roadmap". I find that on one system that
refreshes almost immediately, but on the other three systems, it takes
up to 20 minutes for the icon tree to show up. I can use the Dialog
before the icons appear.
Up to 20 minutes? - well, I never waited that long before deciding there
was some sort of problem.
I was able to use theDialog to connect, so I left it run for a while.
After I came back, the tree was there. After that it worked fine,
until I closed EVFSGUI, and opened it again, then it took another 10
minutes to populate.
Post by Pete Brown
Interestingly it seems to revolve around the fact that Windows has a
"master browser" competition and OS/2 NETBIOS does not. You can test
that by having a win system running on the network - the refresh is
instant then.
No, that doesn't seem to have anything to do with it. I see the same
thing with XP running on one of the systems, and it does appear that
my router takes on that roll when there is no windows system present.
The odd thing is, that the one system with both SAMBA server, and
EVFS, refreshes almost immediately, every time, while the other system
with SAMBA server, and EVFS, takes a long time to refresh. I need to
do more experimenting to see if I can establish a pattern to what is
going on.
I can only report what happens here - and that is precisely nothing as
far as "Network Neighbourhood" is concerned; nothing gets displayed in
that window when running an "eCS only" network.

If I boot Windows2000 in a VPC then the "Network Neighbourhood" does get
populated immediately on starting EVFSgui.


Regards

Pete
Post by Doug Bissett
Post by Pete Brown
Post by Doug Bissett
Samba seems to be working well, but I can't use it exclusively, until
the missing files problem is resolved.
As mentioned above the only current answer seems to be using samba
server instead of OS/2 NETBIOS.
I will try that.
Post by Pete Brown
Post by Doug Bissett
Thanks...
Have fun :-)
It is always fun, but plese let me know if you find a source of 48
hour days :-)
Post by Pete Brown
Pete
Herwig Bauernfeind
2010-01-11 08:41:21 UTC
Permalink
Post by Doug Bissett
Post by Pete Brown
Up to 20 minutes? - well, I never waited that long before deciding there
was some sort of problem.
I was able to use theDialog to connect, so I left it run for a while.
After I came back, the tree was there. After that it worked fine,
until I closed EVFSGUI, and opened it again, then it took another 10
minutes to populate.
There is no caching mechanism in EVFSGUI, so that sounds "normal" - that
sounds very much like at least one of your machines needs ages to
complete the request.

smbtree will tell us - I'll try to provide the proper command line


Kind regards,
Herwig
Herwig Bauernfeind
2010-01-10 10:35:06 UTC
Permalink
Post by Doug Bissett
I am experimenting with SAMBA and EVFS. The results are rather mixed.
On a newly installed eCS 2.0 Silver system, both samba-1-0-3.wpi and
evfsgui-20-GA-20091224.wpi installed, with no trouble, and appear to
be working (but eVFS seems to have a problem - more below).
Since I am not, yet, prepared to commit to SAMBA, I left NETBIOS over
TCP/IP installed on my main system (eCS 2.0 Silver), and just instaled
EVFS. The install appeared to go successfuly, but when I attmpted to
start EVFSGUI, the program appered in the eCenter (LSwitcher), but the
window didn't open, and one processor was at 99%. I also tried EVFS on
an older eCS 1.2 system. Same symptoms (using the older WinList in
eCenter, and only one processor). I was able to kill the program with
CADH, in both cases. After a while, I realized that neither of those
IFS=M:\ECS\BOOT\EVFS.IFS
RUN=M:\ECS\BIN\EVFSCTL.EXE
The reason is that I am not entitled to distribute EVFS.IFS which is
part of eComStation with the EVFSGUI package.
The same applies to Netdrive. You must have either installed EVFS (found
in ESAMBAC.WPI on the eCS CD) or Netdrive installed prior to starting
EVFSGUI.

If either Netdrive or EVFS are present EVFSGUI will start as expected. I
thought I had fixed the endless loop you are obviously seeing, but it
looks I am wrong. I have to revisit this issue once more.

The next eCS 2 release will install EVFS and all components found in
evfsgui-20-GA-20091224.wpi.
The package freely available at netlabs will always come without the
IFS, but will otherwise be compatible.
Post by Doug Bissett
It would also be good if the program itself would warn that the driver is not
running, rather than just hanging.
Absolutely. The next drop should do that.
Post by Doug Bissett
Okay, I got all of that to work. Now, I discovered another rather
serious problem. I have one directory that has 302 files in it, served
by NETBIOS over TCP/IP. When I attempt to display the contents, using
EVFS (the resulting drive object), that directory only shows about 88
files. The other systems show roughly the same number of files (93,
and 98), but not the whole thing. Using a command line against the
drive shows the same as the drive object (even on the same system, but
the real directory shows them all). Using the requester from NETBIOS
over TCP/IP, shows all of the files.
Am I missing something, or is EVFS dropping data, with no warning?
Very interesting. I did tests with Samba Client on IBM Peer Served
directories and did not see this. Could you open a Ticket at
http://svn.netlabs.org/samba and provide as much information (possibly
including logs) as possible and we will look into it.
Post by Doug Bissett
I also like the new "Network Neighborhood", in EVFSGUI, but that does
sound rather windowish :-)
Hehe, indeed. The terminology was intended to be a temporarily one, to
be revised and changed before the release. However I honestly confess, I
forgot about it and right now this cannot be changed, as it went into
all NLV and helpfiles and these should not be changed anymore before...
Post by Doug Bissett
Perhaps it could be named something more appropriate, like "Network Roadmap".
But I'll note it down and it might be changed for EVFSGUI 2.1.
Post by Doug Bissett
I find that on one system that
refreshes almost immediately, but on the other three systems, it takes
up to 20 minutes for the icon tree to show up. I can use the Dialog
before the icons appear.
There are various possibilities why you might see this, it even might be
perfectly normal. The browsing concept is a bit, ummmh, strange. Running
smbtree.exe from the commandline with a higher loglevel would reveal,
where it is waiting....
Post by Doug Bissett
Samba seems to be working well, but I can't use it exclusively, until
the missing files problem is resolved.
I'd suggest using Samba Server on the server side.

I have a bunch of strange reports if the server side is IBM Peer/LAN
Server/WSEB driven, but as I said it appears to work normally here....
Post by Doug Bissett
Thanks...
Thank you for your feedback, it is appreciated.

BTW all the client packages will be updated for several changes and
fixes within the upcoming week.

Regards,
Herwig
Doug Bissett
2010-01-10 16:27:11 UTC
Permalink
On Sun, 10 Jan 2010 10:35:06 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
I am experimenting with SAMBA and EVFS. The results are rather mixed.
On a newly installed eCS 2.0 Silver system, both samba-1-0-3.wpi and
evfsgui-20-GA-20091224.wpi installed, with no trouble, and appear to
be working (but eVFS seems to have a problem - more below).
Since I am not, yet, prepared to commit to SAMBA, I left NETBIOS over
TCP/IP installed on my main system (eCS 2.0 Silver), and just instaled
EVFS. The install appeared to go successfuly, but when I attmpted to
start EVFSGUI, the program appered in the eCenter (LSwitcher), but the
window didn't open, and one processor was at 99%. I also tried EVFS on
an older eCS 1.2 system. Same symptoms (using the older WinList in
eCenter, and only one processor). I was able to kill the program with
CADH, in both cases. After a while, I realized that neither of those
IFS=M:\ECS\BOOT\EVFS.IFS
RUN=M:\ECS\BIN\EVFSCTL.EXE
The reason is that I am not entitled to distribute EVFS.IFS which is
part of eComStation with the EVFSGUI package.
I have no problem with that. ECS does need something to make it worth
buying :-)
Post by Herwig Bauernfeind
The same applies to Netdrive. You must have either installed EVFS (found
in ESAMBAC.WPI on the eCS CD) or Netdrive installed prior to starting
EVFSGUI.
I am not familiar with Netdrive. If it is installed with WarpIn, you
should be able to make the EVFSGUI install dependent on having one, or
the other, installed. Or, you could use a bit of REXX to look for the
un-REMed lines in CONFIG.SYS.
Post by Herwig Bauernfeind
If either Netdrive or EVFS are present EVFSGUI will start as expected. I
thought I had fixed the endless loop you are obviously seeing, but it
looks I am wrong. I have to revisit this issue once more.
It does appear that it is an endless loop.
Post by Herwig Bauernfeind
The next eCS 2 release will install EVFS and all components found in
evfsgui-20-GA-20091224.wpi.
The package freely available at netlabs will always come without the
IFS, but will otherwise be compatible.
Post by Doug Bissett
It would also be good if the program itself would warn that the driver is not
running, rather than just hanging.
Absolutely. The next drop should do that.
Thanks. Please let me know if I can do some testing for you. Almost
usable e-mail address below...
Post by Herwig Bauernfeind
Post by Doug Bissett
Okay, I got all of that to work. Now, I discovered another rather
serious problem. I have one directory that has 302 files in it, served
by NETBIOS over TCP/IP. When I attempt to display the contents, using
EVFS (the resulting drive object), that directory only shows about 88
files. The other systems show roughly the same number of files (93,
and 98), but not the whole thing. Using a command line against the
drive shows the same as the drive object (even on the same system, but
the real directory shows them all). Using the requester from NETBIOS
over TCP/IP, shows all of the files.
Am I missing something, or is EVFS dropping data, with no warning?
Very interesting. I did tests with Samba Client on IBM Peer Served
directories and did not see this. Could you open a Ticket at
http://svn.netlabs.org/samba and provide as much information (possibly
including logs) as possible and we will look into it.
I will try to do that later today...
Post by Herwig Bauernfeind
Post by Doug Bissett
I also like the new "Network Neighborhood", in EVFSGUI, but that does
sound rather windowish :-)
Hehe, indeed. The terminology was intended to be a temporarily one, to
be revised and changed before the release. However I honestly confess, I
forgot about it and right now this cannot be changed, as it went into
all NLV and helpfiles and these should not be changed anymore before...
Post by Doug Bissett
Perhaps it could be named something more appropriate, like "Network Roadmap".
But I'll note it down and it might be changed for EVFSGUI 2.1.
Hopefully, M$ doesn't have that term copywrited...
Post by Herwig Bauernfeind
Post by Doug Bissett
I find that on one system that
refreshes almost immediately, but on the other three systems, it takes
up to 20 minutes for the icon tree to show up. I can use the Dialog
before the icons appear.
There are various possibilities why you might see this, it even might be
perfectly normal. The browsing concept is a bit, ummmh, strange. Running
smbtree.exe from the commandline with a higher loglevel would reveal,
where it is waiting....
Hopefully, it is not "perfectly normal", although I do see a similar
delay in windows (usually leass than 2 minutes though).
Post by Herwig Bauernfeind
Post by Doug Bissett
Samba seems to be working well, but I can't use it exclusively, until
the missing files problem is resolved.
I'd suggest using Samba Server on the server side.
I can probably try that, without changing my current setup.
Post by Herwig Bauernfeind
I have a bunch of strange reports if the server side is IBM Peer/LAN
Server/WSEB driven, but as I said it appears to work normally here....
It always does :-)
Post by Herwig Bauernfeind
Post by Doug Bissett
Thanks...
Thank you for your feedback, it is appreciated.
I was going to try the earlier beta versions, but other things got in
the way. When I saw that the GA was released, I decided that I had
better get to it, or it would be too late :-)
Post by Herwig Bauernfeind
BTW all the client packages will be updated for several changes and
fixes within the upcoming week.
I'll be watching for it...
Post by Herwig Bauernfeind
Regards,
Herwig
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Doug Bissett
2010-01-10 19:22:37 UTC
Permalink
On Sun, 10 Jan 2010 16:27:11 UTC, "Doug Bissett"
Post by Doug Bissett
Post by Herwig Bauernfeind
Post by Doug Bissett
I find that on one system that
refreshes almost immediately, but on the other three systems, it takes
up to 20 minutes for the icon tree to show up. I can use the Dialog
before the icons appear.
There are various possibilities why you might see this, it even might be
perfectly normal. The browsing concept is a bit, ummmh, strange. Running
smbtree.exe from the commandline with a higher loglevel would reveal,
where it is waiting....
Hopefully, it is not "perfectly normal", although I do see a similar
delay in windows (usually leass than 2 minutes though).
I think I have found this problem. Since I don't want applications
installed on my boot drives, I change the target directories in WarpIn
to point to one of my program/data drives. When I install
evfsgui-20-GA-20091224.wpi it forces the install to be on the boot
drive, including a \SAMBA directory, with some utilities (including
smbtree.exe) in it. It also places the x:\SAMBA path in the path
environment vaiable in CONFIG.SYS. When I install samba-1-0-3.wpi it
follows the WarpIn settings, and puts it in my applications directory,
on a different drive (which is as it should be, so that a re-install
of the system will not mess up server configurations). IF
samba-1-0-3.wpi gets installed to the boot drive, it updates the files
that evfsgui-20-GA-20091224.wpi placed in x:\SAMBA (which updates
smbtree.exe). However, if the server gets installed on another drive,
the older smbtree.exe is left in x:\SAMBA, and it is in the path, so
it appears that that is what the system uses. By changing the path
entry to point to the directory as installed by the server, I no
longer seem to have the delay problem.

I need to do other things for a while, so this is a preliminary
report, but this may also explain some other things, like missing
files (still to be tested).

More later...
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Herwig Bauernfeind
2010-01-11 09:03:06 UTC
Permalink
Post by Doug Bissett
I think I have found this problem. Since I don't want applications
installed on my boot drives, I change the target directories in WarpIn
to point to one of my program/data drives. When I install
evfsgui-20-GA-20091224.wpi it forces the install to be on the boot
drive, including a \SAMBA directory, with some utilities (including
smbtree.exe) in it.
The next WPI incarnation will install the commandline utilities into
\ecs\system\samba (decision of the powers behind eCS).
I am not happy with this decision as it imposes IMHO possible problems
with our Samba port.

This new set of the commandline utilities has one fix that eliminates
one problem (upcase tables are also found if the
commandline utilities are NOT installed in \samba, and possibly others,
too):
http://msplins06.bon.at/%7Eadmin139/files/smbclut-3.0.37-os2-20100108.zip

Put an additional environment variable into config.sys:

SET SMB_EXE=x:\whatever_path_to\samba

in order to enable this fix.
Post by Doug Bissett
It also places the x:\SAMBA path in the path
environment vaiable in CONFIG.SYS. When I install samba-1-0-3.wpi it
follows the WarpIn settings, and puts it in my applications directory,
on a different drive (which is as it should be, so that a re-install
of the system will not mess up server configurations). IF
samba-1-0-3.wpi gets installed to the boot drive, it updates the files
that evfsgui-20-GA-20091224.wpi placed in x:\SAMBA (which updates
smbtree.exe). However, if the server gets installed on another drive,
the older smbtree.exe is left in x:\SAMBA, and it is in the path, so
it appears that that is what the system uses. By changing the path
entry to point to the directory as installed by the server, I no
longer seem to have the delay problem
I am aware of this collision (my main emphasis until recently always was
the server).

At the moment there are 2 differences between the incarnations of the
client commandline utilities that come in the standalone package and the
server package:

- The ones in the server package require libc064x.dll, the standalone
ones require libc063.dll (this is preferable).
- The latest and only the latest standalone ones support %SMB_EXE%, the
latest server package does not have this feature yet.

Otherwise there is not difference worth caring about.

Regards,
Herwig
Herwig Bauernfeind
2010-01-11 08:35:14 UTC
Permalink
Hi Doug,
Post by Doug Bissett
Post by Herwig Bauernfeind
The reason is that I am not entitled to distribute EVFS.IFS which is
part of eComStation with the EVFSGUI package.
I have no problem with that. ECS does need something to make it worth
buying :-)
:-)
Post by Doug Bissett
Post by Herwig Bauernfeind
The same applies to Netdrive. You must have either installed EVFS (found
in ESAMBAC.WPI on the eCS CD) or Netdrive installed prior to starting
EVFSGUI.
I am not familiar with Netdrive. If it is installed with WarpIn,
It is not, it has a (quite nice) custom installer....
Post by Doug Bissett
Post by Herwig Bauernfeind
If either Netdrive or EVFS are present EVFSGUI will start as expected. I
thought I had fixed the endless loop you are obviously seeing, but it
looks I am wrong. I have to revisit this issue once more.
It does appear that it is an endless loop.
It was - the last fix attempt was simply not waterproof, I hope this one
is. Please try:
http://msplins06.bon.at/%7Eadmin139/files/evfsgui-201-20100111.zip

Kind regards,
Herwig
Doug Bissett
2010-01-12 04:57:09 UTC
Permalink
On Mon, 11 Jan 2010 08:35:14 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
It does appear that it is an endless loop.
It was - the last fix attempt was simply not waterproof, I hope this one
http://msplins06.bon.at/%7Eadmin139/files/evfsgui-201-20100111.zip
Kind regards,
Herwig
I am sorry to report that it still goes into an endless loop, when the
EVFS.IFS, and EVFSCTL.EXE are not loaded. The system runs at 99.9% and
is very slow to respond. The program itself doesn't open it's window,
but I can get the window to open if I select it from the window list.
I have to kill it with CADH to get it to do anything though. A quick
test shows that it does work fine, when the EVFS stuff is properly
loaded.

Thanks...
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Herwig Bauernfeind
2010-01-12 07:34:37 UTC
Permalink
Post by Doug Bissett
On Mon, 11 Jan 2010 08:35:14 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
It does appear that it is an endless loop.
It was - the last fix attempt was simply not waterproof, I hope this one
http://msplins06.bon.at/%7Eadmin139/files/evfsgui-201-20100111.zip
Kind regards,
Herwig
I am sorry to report that it still goes into an endless loop, when the
EVFS.IFS, and EVFSCTL.EXE are not loaded.
Sh*t, sh*t, sh*t. Will try again :-(
Post by Doug Bissett
The system runs at 99.9% and is very slow to respond.
I'll add a break to make sure the system stays responsive even if it
still manages to run into this endless loop.

I am inclined to dump this code section and rewrite it from scratch.
This is really PITA.

Regards,
Herwig
Doug Bissett
2010-01-12 18:27:20 UTC
Permalink
On Tue, 12 Jan 2010 07:34:37 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
On Mon, 11 Jan 2010 08:35:14 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
It does appear that it is an endless loop.
It was - the last fix attempt was simply not waterproof, I hope this one
http://msplins06.bon.at/%7Eadmin139/files/evfsgui-201-20100111.zip
Kind regards,
Herwig
I am sorry to report that it still goes into an endless loop, when the
EVFS.IFS, and EVFSCTL.EXE are not loaded.
Sh*t, sh*t, sh*t. Will try again :-(
Post by Doug Bissett
The system runs at 99.9% and is very slow to respond.
I'll add a break to make sure the system stays responsive even if it
still manages to run into this endless loop.
I am inclined to dump this code section and rewrite it from scratch.
This is really PITA.
Regards,
Herwig
I have a REXX application, where I need to know if aspinkk.sys is
loaded, or not. To find out I do:
ask=stream('aspinkk$','c','query exists')
If ask is null after that, the driver does not exist. Can you do
something similar?
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Herwig Bauernfeind
2010-01-16 15:06:24 UTC
Permalink
Post by Doug Bissett
On Tue, 12 Jan 2010 07:34:37 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
On Mon, 11 Jan 2010 08:35:14 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
It does appear that it is an endless loop.
It was - the last fix attempt was simply not waterproof, I hope this one
http://msplins06.bon.at/%7Eadmin139/files/evfsgui-201-20100111.zip
Kind regards,
Herwig
I am sorry to report that it still goes into an endless loop, when the
EVFS.IFS, and EVFSCTL.EXE are not loaded.
Sh*t, sh*t, sh*t. Will try again :-(
Post by Doug Bissett
The system runs at 99.9% and is very slow to respond.
I'll add a break to make sure the system stays responsive even if it
still manages to run into this endless loop.
I am inclined to dump this code section and rewrite it from scratch.
This is really PITA.
Regards,
Herwig
I have a REXX application, where I need to know if aspinkk.sys is
ask=stream('aspinkk$','c','query exists')
If ask is null after that, the driver does not exist. Can you do
something similar?
Unfortunately not, as neither EVFS.IFS nor Netdrive seem to have such an
embedded stream to query.

Kind regards,
Herwig
--
Mit freundlichen Grüßen/
With Best Regards

Herwig Bauernfeind
--
+------------------------
| Wirtschaftstreuhänder
| Mag. Herwig Bauernfeind
| Steuerberater
| Martin-Luther-Straße 12
| A-9300 St.Veit a.d.Glan
| Österreich - Austria
| Telefon: ++43 4212 2028
| Fax: ++43 4212 2028 76
Pete Brown
2010-01-16 16:10:52 UTC
Permalink
Hi Herwig
Post by Herwig Bauernfeind
Post by Doug Bissett
On Tue, 12 Jan 2010 07:34:37 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
On Mon, 11 Jan 2010 08:35:14 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
It does appear that it is an endless loop.
It was - the last fix attempt was simply not waterproof, I hope
http://msplins06.bon.at/%7Eadmin139/files/evfsgui-201-20100111.zip
Kind regards,
Herwig
I am sorry to report that it still goes into an endless loop, when the
EVFS.IFS, and EVFSCTL.EXE are not loaded.
Sh*t, sh*t, sh*t. Will try again :-(
Post by Doug Bissett
The system runs at 99.9% and is very slow to respond.
I'll add a break to make sure the system stays responsive even if it
still manages to run into this endless loop.
I am inclined to dump this code section and rewrite it from scratch.
This is really PITA.
Regards,
Herwig
I have a REXX application, where I need to know if aspinkk.sys is
ask=stream('aspinkk$','c','query exists')
If ask is null after that, the driver does not exist. Can you do
something similar?
Unfortunately not, as neither EVFS.IFS nor Netdrive seem to have such an
embedded stream to query.
Kind regards,
Herwig
An alternative suggestion to checking whether evfs.ifs and evfsctl.exe
or netdrive variations are loaded/running: Check config.sys has the
necessary lines - with no REM at the start.

Regards

Pete
Doug Bissett
2010-01-17 02:59:54 UTC
Permalink
On Sat, 16 Jan 2010 16:10:52 UTC, Pete Brown
Post by Pete Brown
Hi Herwig
Post by Herwig Bauernfeind
Post by Doug Bissett
On Tue, 12 Jan 2010 07:34:37 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
On Mon, 11 Jan 2010 08:35:14 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
It does appear that it is an endless loop.
It was - the last fix attempt was simply not waterproof, I hope
http://msplins06.bon.at/%7Eadmin139/files/evfsgui-201-20100111.zip
Kind regards,
Herwig
I am sorry to report that it still goes into an endless loop, when the
EVFS.IFS, and EVFSCTL.EXE are not loaded.
Sh*t, sh*t, sh*t. Will try again :-(
Post by Doug Bissett
The system runs at 99.9% and is very slow to respond.
I'll add a break to make sure the system stays responsive even if it
still manages to run into this endless loop.
I am inclined to dump this code section and rewrite it from scratch.
This is really PITA.
Regards,
Herwig
I have a REXX application, where I need to know if aspinkk.sys is
ask=stream('aspinkk$','c','query exists')
If ask is null after that, the driver does not exist. Can you do
something similar?
Unfortunately not, as neither EVFS.IFS nor Netdrive seem to have such an
embedded stream to query.
Kind regards,
Herwig
An alternative suggestion to checking whether evfs.ifs and evfsctl.exe
or netdrive variations are loaded/running: Check config.sys has the
necessary lines - with no REM at the start.
Regards
Pete
That may not be 100%, since there could be some reason why the lines
are present, but the driver fails to operate, but it is one way to
check if it should be working. You could also check to see if
EVFSCTL.EXE is running.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Herwig Bauernfeind
2010-01-18 07:17:16 UTC
Permalink
Post by Doug Bissett
On Sat, 16 Jan 2010 16:10:52 UTC, Pete Brown
Post by Pete Brown
Hi Herwig
Post by Herwig Bauernfeind
Post by Doug Bissett
On Tue, 12 Jan 2010 07:34:37 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
On Mon, 11 Jan 2010 08:35:14 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
It does appear that it is an endless loop.
It was - the last fix attempt was simply not waterproof, I hope
http://msplins06.bon.at/%7Eadmin139/files/evfsgui-201-20100111.zip
Kind regards,
Herwig
I am sorry to report that it still goes into an endless loop, when the
EVFS.IFS, and EVFSCTL.EXE are not loaded.
Sh*t, sh*t, sh*t. Will try again :-(
Post by Doug Bissett
The system runs at 99.9% and is very slow to respond.
I'll add a break to make sure the system stays responsive even if it
still manages to run into this endless loop.
I am inclined to dump this code section and rewrite it from scratch.
This is really PITA.
Regards,
Herwig
I have a REXX application, where I need to know if aspinkk.sys is
ask=stream('aspinkk$','c','query exists')
If ask is null after that, the driver does not exist. Can you do
something similar?
Unfortunately not, as neither EVFS.IFS nor Netdrive seem to have such an
embedded stream to query.
An alternative suggestion to checking whether evfs.ifs and evfsctl.exe
or netdrive variations are loaded/running: Check config.sys has the
necessary lines - with no REM at the start.
That may not be 100%, since there could be some reason why the lines
are present, but the driver fails to operate, but it is one way to
check if it should be working. You could also check to see if
EVFSCTL.EXE is running.
Currently it is a bit of mixture:

Basically I am attempting to register the REXX functions for one, if
that fails I try the other one.
In addtion I try to restart EVFSCTL.EXE (but not NDCTL.EXE (which is
bad) ) in case it is not running (due to a crash or whatever).
Plus there's the -nfds force switch.

Obviously there is a chance to get lost somewhere and start that over
and over again.

A clean reimplementation is the way to go.

Kind regards,
Herwig
Doug Bissett
2010-01-18 18:14:49 UTC
Permalink
On Mon, 18 Jan 2010 07:17:16 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
On Sat, 16 Jan 2010 16:10:52 UTC, Pete Brown
Post by Pete Brown
Hi Herwig
Post by Herwig Bauernfeind
Post by Doug Bissett
On Tue, 12 Jan 2010 07:34:37 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
On Mon, 11 Jan 2010 08:35:14 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
It does appear that it is an endless loop.
It was - the last fix attempt was simply not waterproof, I hope
http://msplins06.bon.at/%7Eadmin139/files/evfsgui-201-20100111.zip
Kind regards,
Herwig
I am sorry to report that it still goes into an endless loop, when the
EVFS.IFS, and EVFSCTL.EXE are not loaded.
Sh*t, sh*t, sh*t. Will try again :-(
Post by Doug Bissett
The system runs at 99.9% and is very slow to respond.
I'll add a break to make sure the system stays responsive even if it
still manages to run into this endless loop.
I am inclined to dump this code section and rewrite it from scratch.
This is really PITA.
Regards,
Herwig
I have a REXX application, where I need to know if aspinkk.sys is
ask=stream('aspinkk$','c','query exists')
If ask is null after that, the driver does not exist. Can you do
something similar?
Unfortunately not, as neither EVFS.IFS nor Netdrive seem to have such an
embedded stream to query.
An alternative suggestion to checking whether evfs.ifs and evfsctl.exe
or netdrive variations are loaded/running: Check config.sys has the
necessary lines - with no REM at the start.
That may not be 100%, since there could be some reason why the lines
are present, but the driver fails to operate, but it is one way to
check if it should be working. You could also check to see if
EVFSCTL.EXE is running.
Basically I am attempting to register the REXX functions for one, if
that fails I try the other one.
In addtion I try to restart EVFSCTL.EXE (but not NDCTL.EXE (which is
bad) ) in case it is not running (due to a crash or whatever).
Plus there's the -nfds force switch.
Obviously there is a chance to get lost somewhere and start that over
and over again.
A clean reimplementation is the way to go.
Kind regards,
Herwig
I would guess that the problem is with trying to restart EVFSCTL.EXE.
If the EVFS.IFS is not loaded, that will always fail. I suppose it is
looping, trying to restart EVFSCTL.EXE, but I can't prove that.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
David McKenna
2010-01-10 14:26:18 UTC
Permalink
Hi Doug,

On Sat, 9 Jan 2010 23:52:32 +0000 (UTC), Doug Bissett wrote:

-snip-
Post by Doug Bissett
appropriate, like "Network Roadmap". I find that on one system that
refreshes almost immediately, but on the other three systems, it takes
up to 20 minutes for the icon tree to show up. I can use the Dialog
before the icons appear.
This may be a long shot, but go to this page:
http://svn.netlabs.org/samba/wiki/FAQ and scroll down to the bottom and read
the section starting with 'Marcel Muller wrote". Maybe related to your
slowness problem??

Dave McKenna
Doug Bissett
2010-01-10 16:27:13 UTC
Permalink
On Sun, 10 Jan 2010 14:26:18 UTC, "David McKenna"
Post by David McKenna
Hi Doug,
-snip-
Post by Doug Bissett
appropriate, like "Network Roadmap". I find that on one system that
refreshes almost immediately, but on the other three systems, it takes
up to 20 minutes for the icon tree to show up. I can use the Dialog
before the icons appear.
http://svn.netlabs.org/samba/wiki/FAQ and scroll down to the bottom and read
the section starting with 'Marcel Muller wrote". Maybe related to your
slowness problem??
Dave McKenna
Interesting, but that doesn't really seem to be related. Once I do get
connected, it all seems to be working quite well. I haven't done any
speed testing, but performance seems to be similar to what I see with
NETBIOS over TCP/IP.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Herwig Bauernfeind
2010-01-11 08:43:41 UTC
Permalink
Post by Doug Bissett
On Sun, 10 Jan 2010 14:26:18 UTC, "David McKenna"
Post by David McKenna
Hi Doug,
-snip-
Post by Doug Bissett
appropriate, like "Network Roadmap". I find that on one system that
refreshes almost immediately, but on the other three systems, it takes
up to 20 minutes for the icon tree to show up. I can use the Dialog
before the icons appear.
http://svn.netlabs.org/samba/wiki/FAQ and scroll down to the bottom and read
the section starting with 'Marcel Muller wrote". Maybe related to your
slowness problem??
Dave McKenna
Interesting, but that doesn't really seem to be related. Once I do get
connected, it all seems to be working quite well. I haven't done any
speed testing, but performance seems to be similar to what I see with
NETBIOS over TCP/IP.
Unfortunately you'd be lucky if you experience the same speed - our
Samba Client is still slower than LAN Requester.
Our Samba Server however outperforms both IBM Peer/LANServer/WSEB on the
same hardware by factors.

Regards,
Herwig
Doug Bissett
2010-01-12 04:35:00 UTC
Permalink
On Mon, 11 Jan 2010 08:43:41 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Unfortunately you'd be lucky if you experience the same speed - our
Samba Client is still slower than LAN Requester.
Our Samba Server however outperforms both IBM Peer/LANServer/WSEB on the
same hardware by factors.
I suspect that the speed is pretty much the same, because my network
runs at 100 Mbs, because of a number of things. The slower systems do
seem to be a bit slower, but not enough to worry about. I do need to
find some time to do more testing, but I have been busy trying to
figure out the best way to use this stuff, and to get the rest of my
systems converted.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Doug Bissett
2010-01-18 05:00:33 UTC
Permalink
On Tue, 12 Jan 2010 04:35:00 UTC, "Doug Bissett"
Post by Doug Bissett
On Mon, 11 Jan 2010 08:43:41 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Unfortunately you'd be lucky if you experience the same speed - our
Samba Client is still slower than LAN Requester.
Our Samba Server however outperforms both IBM Peer/LANServer/WSEB on the
same hardware by factors.
I suspect that the speed is pretty much the same, because my network
runs at 100 Mbs, because of a number of things. The slower systems do
seem to be a bit slower, but not enough to worry about. I do need to
find some time to do more testing, but I have been busy trying to
figure out the best way to use this stuff, and to get the rest of my
systems converted.
I think I need to retract what I said. EVFS is quite a bit slower,
when forming the file tree in the psuedo drive. Watching the
IPMONITOR, it seems that IP activity operates between 20 and 50 Kb/s
when the tree is loading. Once that is done, any actual file transfers
seem to happen at the normal speed. Using windows as a client, on the
other hand, seems to be quite fast, which indicates that it is not the
SAMBA server that is slow, it is EVFS that is slow.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Herwig Bauernfeind
2010-01-18 07:08:34 UTC
Permalink
Post by Doug Bissett
On Tue, 12 Jan 2010 04:35:00 UTC, "Doug Bissett"
Post by Doug Bissett
On Mon, 11 Jan 2010 08:43:41 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Unfortunately you'd be lucky if you experience the same speed - our
Samba Client is still slower than LAN Requester.
Our Samba Server however outperforms both IBM Peer/LANServer/WSEB on the
same hardware by factors.
I suspect that the speed is pretty much the same, because my network
runs at 100 Mbs, because of a number of things. The slower systems do
seem to be a bit slower, but not enough to worry about. I do need to
find some time to do more testing, but I have been busy trying to
figure out the best way to use this stuff, and to get the rest of my
systems converted.
I think I need to retract what I said. EVFS is quite a bit slower,
when forming the file tree in the psuedo drive. Watching the
IPMONITOR, it seems that IP activity operates between 20 and 50 Kb/s
when the tree is loading. Once that is done, any actual file transfers
seem to happen at the normal speed. Using windows as a client, on the
other hand, seems to be quite fast, which indicates that it is not the
SAMBA server that is slow, it is EVFS that is slow.
The culprit is the structure of EVFS vs. ndpsmb.dll, there are many
context switches and this makes things slow. 1.5 is much faster than 1.0
in this respect (integration of smbcd.exe into ndpsmb.dll -> less
context switches).

In addition we see a server issue, which is not fully understood yet:
Reading lots of small files/portions of data is somewhat slow on the
server side, resulting in for example slow speed when reading server
stored Windows profiles and slow reading of Thunderbird profiles.For
most applications however the Samba Server is really fast.

Kind regards,
Herwig
Doug Bissett
2010-01-18 18:14:47 UTC
Permalink
On Mon, 18 Jan 2010 07:08:34 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Post by Doug Bissett
On Tue, 12 Jan 2010 04:35:00 UTC, "Doug Bissett"
Post by Doug Bissett
On Mon, 11 Jan 2010 08:43:41 UTC, Herwig Bauernfeind
Post by Herwig Bauernfeind
Unfortunately you'd be lucky if you experience the same speed - our
Samba Client is still slower than LAN Requester.
Our Samba Server however outperforms both IBM Peer/LANServer/WSEB on the
same hardware by factors.
I suspect that the speed is pretty much the same, because my network
runs at 100 Mbs, because of a number of things. The slower systems do
seem to be a bit slower, but not enough to worry about. I do need to
find some time to do more testing, but I have been busy trying to
figure out the best way to use this stuff, and to get the rest of my
systems converted.
I think I need to retract what I said. EVFS is quite a bit slower,
when forming the file tree in the psuedo drive. Watching the
IPMONITOR, it seems that IP activity operates between 20 and 50 Kb/s
when the tree is loading. Once that is done, any actual file transfers
seem to happen at the normal speed. Using windows as a client, on the
other hand, seems to be quite fast, which indicates that it is not the
SAMBA server that is slow, it is EVFS that is slow.
The culprit is the structure of EVFS vs. ndpsmb.dll, there are many
context switches and this makes things slow. 1.5 is much faster than 1.0
in this respect (integration of smbcd.exe into ndpsmb.dll -> less
context switches).
Reading lots of small files/portions of data is somewhat slow on the
server side, resulting in for example slow speed when reading server
stored Windows profiles and slow reading of Thunderbird profiles.For
most applications however the Samba Server is really fast.
Kind regards,
Herwig
Thanks for that. I think that some serious effort is required to fix
these problems. It seems that eCS requires some sort of replacement
for the older NETBIOS, and SAMBA would seem to be the answer. However,
if it won't perform adequately, that will turn off many people, and we
don't have enough left to be able to lose more without serious
consequences.

Overall, SAMBA seems to be working well. The problems seem to be in
EVFS, but the whole thing is usable, even if it is a little slow at
doing some things.
--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)
Herwig Bauernfeind
2010-01-11 08:37:06 UTC
Permalink
Post by David McKenna
Hi Doug,
-snip-
Post by Doug Bissett
appropriate, like "Network Roadmap". I find that on one system that
refreshes almost immediately, but on the other three systems, it takes
up to 20 minutes for the icon tree to show up. I can use the Dialog
before the icons appear.
http://svn.netlabs.org/samba/wiki/FAQ and scroll down to the bottom and read
the section starting with 'Marcel Muller wrote". Maybe related to your
slowness problem??
No, this is something different. This is for raw data transfer rate with
Samba 3.2 or better and IBM LAN Requester.

Herwig B.
Loading...