[febs]

the new smb implementation that works so good with windows shares doesn't so with samba 2.28 in openbsd operating system.
it is a little bit faster while browsing directories, but it is not while playing media!
it hangs every about 7-8 seconds for 2-3 secs of silence.
no good
thank you very much for paying attention
febs

[darkie]

could you paste some of the logfile from "samba 2.28 in openbsd" that could be important?

[febs]

i cut and paste the logfiles in /var/log/:

log.smbd (nothing interesting in here i think):

[2003/12/10 20:51:26, 0] /usr/obj/i386/samba-2.2.8a/samba-2.2.8a/source/smbd/server.c:main(791)
smbd version 2.2.8a started.
copyright andrew tridgell and the samba team 1992-2002

btw, the samba version is 2.2.8, not 2.28.
log.nmbd is longer, but it does not have no recent log.

please tell me how can i help debugging. can a tcpdump log be useful?
ty!

[darkie]

you could try setting log level higher (for ex. 10 or 20) in smb.conf to capture more debug messages

[febs]

i'lldo that right after finishing posting this . i have tested it on a linux machine with samba3 and it's fast light a thunderbolt!
the machine with openbsd (the server up all time) is an old p133.
perhaps the new implementation is more cpu-hungry and so *this* is the problem?

thanx, i will let you know if i will have more significant logs, and which

[febs]

i'm lost in all these logs. hope these messages of smbd.xbox (the only ones that seems interesting to me) are helpful:

[2004/01/11 02:07:59, 10] /usr/obj/i386/samba-2.2.8a/samba-2.2.8a/source/lib/util_sock.c:receive_smb(609)
receive_smb: length < 0 !
[2004/01/11 02:07:59, 3] /usr/obj/i386/samba-2.2.8a/samba-2.2.8a/source/smbd/process.c:timeout_processing(1073)
receive_smb error (connection reset by peer) exiting
[2004/01/11 02:07:59, 3] /usr/obj/i386/samba-2.2.8a/samba-2.2.8a/source/smbd/sec_ctx.c:set_sec_ctx(329)
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
[2004/01/11 02:07:59, 3] /usr/obj/i386/samba-2.2.8a/samba-2.2.8a/source/smbd/connection.c:yield_connection(48)
yielding connection to
[2004/01/11 02:07:59, 5] /usr/obj/i386/samba-2.2.8a/samba-2.2.8a/source/smbd/oplock.c:receive_local_message(108)
receive_local_message: doing select with timeout of 1 ms
[2004/01/11 02:07:59, 3] /usr/obj/i386/samba-2.2.8a/samba-2.2.8a/source/smbd/server.c:exit_server(545)
server exit (normal exit)
[2004/01/11 02:10:43, 6] /usr/obj/i386/samba-2.2.8a/samba-2.2.8a/source/param/loadparm.c:lp_file_list_changed(2302)
lp_file_list_changed()
file /etc/samba/smb.conf -> /etc/samba/smb.conf last mod_time: sun jan 11 01:54:17 2004

thanx again

[darkie]

you could try playing a file from your openbsd pc on a windows machine with mplayer to see if that works ok. if it doesn't, then your p133 is to slow  :d

[febs]

it plays smoothly by accessing it from a pc!
and it did the same with the old implementation.

what the f**k can it be ?

[darkie]

hmm, you could try the next thing
first make sure you have disabled hd spindown (set to 0)
then create a directory in xbmc called smb. in that dir you should place a file called smb.conf (xbmchome\smb\smb.conf)
the file should have the following contents

  [global]
     workgroup = lan
     server string = xbox
     socket options = so_rcvbuf=8192 so_sndbuf=8192
     debug level = 0

you could try some other options for "sockets options".

[febs]

first make sure you have disabled hd spindown (set to 0)

her, sorry. what's that?
do you talk about hdd going stand-by after some time?

then create a directory in xbmc called smb.

it's already there - if this can matter

in that dir you should place a file called smb.conf

done. with the settings you suggested it does not works.
i have also tried with these values, in this order (i'm updating the post while experimentig):
16384 (it did'nt almost browse the folders)
32768 (perhaps worse)
8242 (still bad. pheraps a little better while playing, slow while browsing)
4121 (nah)
2060 (it can't almost browse the share at all! it works one time each about 5 times)

btw, i checked the status of the processes, and the samba daemon on the server never uses more than 10% of the cpu while playing. so it shouldn't be that.
(while *browsing* folders, the cpu usage grows up tp 70%).
should i try more socket options values? what else can i do?
thanx again

[darkie]

do you talk about hdd going stand-by after some time?

yes

all options can be find at
http://us1.samba.org/samba/docs/man/smb.conf.5.html
note that only the options for the samba client will work, such as

read size = 8192

if none of this work, then i'm out of ideas atm.

[tslayer]

why don't you just try and upgade samba to 3.0.1 on your server?

ts

[febs]

too bad i can't. it won't install on openbsd 3.4 systems. i'm starting to think to change the whole os :-(

thanx all

[febs]

while samba 3.0.0 didn't worked, version 3.0.1 does!
too bad it keep hanging (less than before, but it does so.).
i cannot understand why. the cpu usage is about 19%.

sigh