On Wed, Jul 19, 2006 at 04:00:00PM +0200, Andreas Haumer wrote:
Any comments?
No, except a big thanks for this analysis. It is always nice
to see that this completely paranoid hunt for the 100%
compatibility that can be very exhausting sometimes does pay
off.
Volker
pgpegj0YC0xxy.pgp
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
It's quite a few days since my last message to the Samba mailing
list and there were no useful replies to my previous messages since.
I took me several days of hard work but it seems now I have found
the reason for the problem and so I'll reply
On Wed, Jul 19, 2006 at 04:00:00PM +0200, Andreas Haumer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
It's quite a few days since my last message to the Samba mailing
list and there were no useful replies to my previous messages since.
I took me several days of hard work
Andreas Haumer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[...]
read_file (daten/covers/dhm_offset/o1000c/arc.adf): pos = 1536, size = 512,
returned 512
read_file (daten/covers/dhm_offset/o1000c/arc.adf): pos = 2048, size = 512,
returned 512
read_file
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Martin,
many thanks for your reply!
Martin Zielinski schrieb:
Andreas Haumer wrote:
[...]
The main question IMHO still ist: why does the application
request the files differently when changing the Samba server
operating system (and the Samba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tobias,
thank you for reply!
Tobias Bluhm schrieb:
Another shot in the dark . . . .
and I don't believe you've stated what fs type your using, but have you
tried storing the data using other fs types or playing with the mount
options?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi!
For some months now I'm hunting a Samba performance problem
without a solution yet.
Now I'm hoping someone on this list has an idea (In fact,
I already reported the problem to the mailing list but got
only one reply which did not help)
So I'm
I tried to compare samba settings and made them identical
on both Solaris and Linux samba servers (the only difference
now is printer command strings, but printing is disabled anyway).
Result: no change in runtime behaviour.
I tried to play with Samba settings on the Linux server:
*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Paul!
Many thanks for your reply!
Paul Gienger schrieb:
I don't suppose you've tried messing around with the socket options? E.g.
socket options = TCP_NODELAY SO_SNDBUF=8192
Just a thought.
Thanks, but I've tried that already, too (I
Another shot in the dark . . . .
and I don't believe you've stated what fs type your using, but have you
tried storing the data using other fs types or playing with the mount
options?
-
toby bluhm
philips medical systems, cleveland ohio
10 matches
Mail list logo
