RE: [Samba] Very dumb question
>Maybe this is crayziness, but... >is there a way through some smb.conf script, or any other mean than >installing a graphical interface in the server, as my users are lobying me >:P, to a user of a domain records a data CD with data from the Samba >shares ? Huh? -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] testparm -s
>>Unknown parameter encountered: "passdb backend" >Was this a typo in the email or is this exactly what you have in the smb.conf >file? There should be an equal sign between the words. Gary, "passdb backend" is the name of the parameter, not the parameter and value. Matthew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] testparm -s
>When I check my smb.conf file using the testparm -s command I get these messages >Unknown parameter encountered: "passdb backend" Mark: I'm assuming since it's in the smb.conf file that you need it. If you don't obviously take it out. What section is that parameter in? A share section or your globals section? It should be in the globals. Matthew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Newbie smb.conf question
Excuse my ignorance please, and the simple nature of this questions...but would someone explain to me the difference between the "create mode" and "force create mode" parameters in the smb.conf file? When would "create mode" *not* be forced? Thanks! Matthew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Samba consuming massive amounts of memory (CONT)
>>The process listing does not show Smbd consuming the memory. "free -m" just >>reports a drastic increase when I use Samba. >This probably is only the file cache using the previously unallocated memory. Holger: That's exactly what I thought. However, when all of the memory is finally consumed, I can no longer copy files from the samba share to my Win2K box. Windows says, "Cannot read from source file or disk". When I reboot the machine, it works perfectly. Thanks! Matthew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba consuming massive amounts of memory (CONT)
Concerning Samba consuming memory, I forgot to add one thing, sorry. The process listing does not show Smbd consuming the memory. "free -m" just reports a drastic increase when I use Samba. Relevant portions of ps -fwaux: root 6412 0.0 0.0 10060 2548 ?S08:01 0:00 /usr/sbin/smbd -D -s /etc/samba/smb.conf reisuser 6478 0.0 0.0 10420 3136 ?S08:01 0:00 \_ /usr/sbin/smbd -D -s /etc/samba/smb.conf root 6702 0.0 0.0 10436 3560 ?S08:04 0:00 \_ /usr/sbin/smbd -D -s /etc/samba/smb.conf root 6703 0.0 0.0 10428 3368 ?S08:04 0:00 \_ /usr/sbin/smbd -D -s /etc/samba/smb.conf root 6788 1.8 0.1 10908 4172 ?S08:07 0:19 \_ /usr/sbin/smbd -D -s /etc/samba/smb.conf Thanks you! Matthew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
[Samba] Samba consuming massive amounts of memory
Hi everyone. uname -a: Linux hotbox 2.4.21-15.ELsmp #1 SMP Thu Apr 22 00:18:24 EDT 2004 i686 i686 i386 GNU/Linux smbd -V: Version 3.0.2-6.3E When I use Samba from my Win2K box for anything...listing files, copying files, etc, the amount of used system memorys shoots up VERY quickly. At reboot, memory usage was 195 MB. I copied a 1 GB file over Samba to my Win2K box and memory usage shot up to 1205 MB by the end of the copy. As memory consumptions continues to rise, Samba's performance drops drastically and Windows begins to give weird errors when trying to use shares...file corruptions, unable to connect, etc. I set a limit in the limits.conf file to 50 MB per user...but that doesn't seem to be stopping Samba. What's going on?? Thanks! Matthew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] Please help
>I am using Redhat Linux 9 and configured it as Samba sever.When I tried to >open files on windows network an error message is coming like "Cannot open >files in Samba locations, you can copy those files and try to open in the >linux machine". Hi Anil. Can you show us your smb.conf file? Also, what does the EXACT error message say that Windows is giving you? Matthew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] File corruption
>Now, about once every week or so, we get a file corruption, and last week (even after >upgrading some NICs) seemed to be even worse, with 5 or 6 problems. >Because we had no problems before changing servers, I think hardware errors >are probably not to blame, Hi Warren! Unfortunately, I don't know that I have a good answer for you, but I thought I'd share this. We too have been experiencing EXACTLY what you have described this past two weeks...seemingly random file corruption. We're running Samba 3 on a RedHat Linux 9.0 box. We temporarily switched to NFS but that turned out to be more of a nightmare than Samba (for us anyway). Finally, after googling for hours and posting to this list, we decided to try and trouble shoot the problem on a lower level the best we knew how. There are three main things you can try that might reveal some clues as to what's going on. Maybe you've tried them already. 1) Use strace to start smbd or attach it to a already running child process. If you have a general idea of when or under what circumstances these corruptions occurr, that would be a good time to fire it off because it spits out a insane amount of data. 2) Turn Samba's log level to 3. Again, do that around the time you think corruptions may occurr. Logging level 3 is VERY intense on your server and will definately effect performance. 3) Use ethereal to capture and examine the network traffic. Look through the SMB packets and see what you can see. Of course, all those things really only help if you can reproduce the problem to some degree. We had our hopes set high on strace, but after having experienced a known kernel bug, we could not use it. Since we had spent so much time on the problem, we upgraded to RedHat Enterprise Edition...all the problems vanished immediately. Hope this helps a little! Matthew Connor -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
RE: [Samba] strace
>could you do a closer look at your smbd (maybe with truss or strace) >to see what exactly happens? Hi Chris. Do you mind if I butt in on this thread? I am currently fighting tooth and nail with Samba and I am attempting to do an strace on it myself...to no avail. When I start Samba with "strace -ff -o trace.out smbd -D", the program starts, but I cannot connect to the service on my Windows box. If I start it up without strace and then run strace to try and attach it to the process id, all I get is "ptrace: Operation not permitted" and then the process hangs so hard, even kill -9 smbd won't work! I still having these process hanging in memory. How in the world can I strace samba? Thanks! Matthew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
