search for: smbds

Hi, I am trying to setup two Samba daemons (smbd) on one machine. I would like to have one smbd use configuration file A and the second smbd use configuration file B. Configuration file A will be setup for users home directories and would use security = USER. Configuration file B is for a shared printer and would use security = SHARE. The machine running Samba has aliasing, so I thought I

Hello! I can't find the cause of the above problem. Some smbd processes stuck in close_wait state and some file locks remain behind too. /any clue would be apreciated Attila /

Over the past 2 days, my smbd processes are multiplying worse than rabbits. At least with rabbits it's easy to tell why you wind up with so many... Here's the setup: Samba version 3.2.8-0.24 installed via rpm on a FC6 box with 2 nics, both on the same subnet. The samba server acts as a PDC in a mixed environment but mostly windows pc's running xp. It is used mostly for file

...Tue, Aug 30, 2016 at 10:39:04AM -0400, Jim Ballantine via samba wrote: > We are running a Red Hat Linux 6 system with samba 3.6.23 installed, and > configured as a stand alone > server. A couple of users are either spawning excessive numbers of smbd, > or failing to kill them Is this smbds in "D" state? If so, please contact RedHat. That's a kernel bug, or something below like a failed disk. Volker

[This is a discussion that started earlier about automounter] John Posenau wrote: > What I've found so far is that the windows client (any machine, roving > profile) with this user's account authenticates in a samba domain on machine > A. His files are located on machine B (not running Samba). Machine A > automount his nisplus_home. A little indirection but hey. As

I have an open PMR with IBM regarding a slowness issue when more than 450 smbds are trying to login and download roaming profiles. The system is a 6H1 with 6 RS64-III 668MHz cpus and 6 GB memory w/Gb ethernet. We have over 10,000 student accounts with roaming profiles and 800 XP-SP1 workstations for them to choose from. I've compiled 2.2.7a in 64 bit and 32 bit modes. R...

...(via filesystem copy), added and set the driver without errors. But getdriver reports no driver associatet with the printer?! So reports below. I am sure, this was working on this system. I tried to reinit the ntprinters.tdb, printing.tdb, nt_forms.tdb and ntdrivers.tdb by removing and HUPPING all smbds (a plenty of users are on the server so I could not restart smbd cleanly). Can anybody give me some advice. Thanks Gernot PS Maybe an issue: I copied, added, and set the driver several times in a script (W32X86 WIN40 for each printer of the same type!) <begin> atlas# rpcclient -U root%s...

Hi Alexander, Not sure if this of any help, but we had a similar problem with runaway SMBDs and what seemed to be oplocks. We are running RH6.2 with 0.7.26 ACLs. After much messing around and hassling Jeremy, I eventually changed the kernel from 2.2.19 to 2.2.20 and recompiled everything from scratch. Since then we have not had one of these rogue processes. I think Jeremy was right whe...

I've noticed that my W2K clients connect to Samba much more quickly if I run it on port 445 instead of 139. However, my WNT clients then won't connect at all. I read somewhere that it was possible to forward the requests on port 139 to port 445. Anyone know how to do this or how to listen to both ports simultaneously? Thanks, Jason Joines Open Source = Open Mind

Dear all, A while ago I posted a message regading the way Samba is behaving and some problems that I was facing with Windows "loosing" the connection with the server... Here is another sample of what my /var/log/messages still looks like: Sep 19 15:08:01 Srv smbd-classic[3499]: [2004/09/19 15:08:01, 0] lib/util_sock.c:read_data(436) Sep 19 15:08:01 Srv smbd-classic[3499]:

...:49:31, 1, pid=13874, effective(0, 0), real(0, 0)] smbd/service.c:close_cnum(836) atpc4dcc (158.226.226.71) closed connection to service vobstore so my question now: how can it happen that smbd holds the lock for secrets.tdb while waiting for any data from network and therefore block all other smbds?? what could be the reason for this behaviour? and (most important :-)) how can i avoid this? thanks and merry xmas to everyone! christian p.s.: sorry if i cannot be any clearer... as this is a life-system i always have to resolve this problem very fast (kill all smbds and restart samb...

...t and hence moving from NFS for our Sun fileservers to Samba. I have seen figures indicating Samba is as good NT for SMB service. However what we are concerned with is: a) relative performance of Samba vs Sun's NFS b) loading on servers with lots of active connections (and hence lots of smbds). Do you need more memory than with comparable NFS set up? Do you need more processing power? Any pointers to results or hints gratefully received. I realise things are complicated by the ever increasing power of the clients (ie moving from mixed 486/pentium Win 3.1 to pentium NT client base)....

I'm still having some problems with 1.9.18p10 on a DEC Unix 4.0e machine (this machine was upgraded from 4.0d last week). The smbds can take up to 20% of the cpu at various times. Anyways, I've been through all this before with the mailing list and a number of people who have attempted to help me out. Thanks to all of you. But, I have some more info which may or may not be useful. Today I decided to try a debug level = 9...

...d the same smb.conf and now I'm having some irritating problems: every few hours all smbd's simply stop answering, although they keep lurking in the background, and no new smbd gets started. All my 70 users get DOS error messages at the same time, my phone starts ringing, I kill -15 all the smbds, restart them and everyghint works fine till next time. What's irritating is that this problems leaves no traces in either Samba's or Linux's logs; during these events I can see nothing wrong with the machine - there's plenty of memory, swap and resources. Anyone have any ideas th...

...installed samba-server (1.9.18, supplied with Red Hat 5.2) and everything worked fine. Then I added a DNS (named) at the same machine, just as an experiment. Now samba became unfriendly. The DNS seems to perform very well (nslookup), so I guess nothing is wrong with /etc/resolv.conf. Also, no other smbds have been started. Then I performed the 10 tests. On test 3 I got the "unfriendly" message. Testparm didn't find any errors. Nmblookup also reported no errors."smbclient '\\<server>\<dir>'" failed, as did "net view \\<server>" and "ne...

...installed samba-server (1.9.18, supplied with Red Hat 5.2) and everything worked fine. Then I added a DNS (named) at the same machine, just as an experiment. Now samba became unfriendly. The DNS seems to perform very well (nslookup), so I guess nothing is wrong with /etc/resolv.conf. Also, no other smbds have been started. Then I performed the 10 tests. On test 3 I got the "unfriendly" message. Testparm didn't find any errors. Nmblookup also reported no errors."smbclient '\\<server>\<dir>'" failed, as did "net view \\<server>" and "ne...

Hi Everyone -- Currently we are running two samba servers, server1 and server2 for example, which are each using the same smb.conf.editme as an include file to the server's smb.conf file for it's shares. In other words if you go to \\server1\my-share or \\server2\my-share, it would be the identical share. One quite large problem that we are running into is that although each server

Is there a way to grant a user rights to a directory without restarting samba ? thx, Mark

Hi list, I am planning to deploy samba 2.2.6 on a two-node cluster running Tru64 UNIX 5.1A. Each node will be running an instance of samba providing different services, but I want the locks directory to be shared between them so that if one node goes down, the other can take over its services and still have correct information about open files etc. My question: Can the tdb's handle being

...allation with periodically dying nmbds. Since the customer didn't call again regarding these problems I had the opinion that everything is fine .... Today the customer called and mentioned that there are additional problems. He had fixed the nmbd problem everyday by rebooting .... :-) Now the smbds also start to die. Again no pattern. No way to reproduce. But there were strange entries in the logs linux smbd[8311]: smbd/oplock.c process_local_message(418) linux smbd[8311]: process localmessage: unknown UDP message command code (e393) ignoring with different command codes i.e. 1e73, 2b94 a...