similar to: Multiple processes of smbd spawning...don't know why

I've currently got a samba 4.0.6-GIT-3f8ea16 deployment that's spawning many (250 or more) smbd processes whenever a backup runs and starts backing up files that have samba ACL's attached to them. (Such as the 'sysvol' volume) This will effectively lock up the machine until I've restarted samba and killed the backup job. If the backup is still running, samba will

> > I can't find any posts on this list for peoples using quota_over_flag > > > > http://wiki2.dovecot.org/Quota/Configuration#Overquota-flag_.28v2.2.16.2B-.29 > > > > If my userdb is sql what would be best script to use in terms of performance? > > (I mean if over-quota-flag triggers script every time it changes and the script > > calls CLI mysql

Hi, I am using a cluster with LAM 7.1.3/MPI 2 and R 2.6.0. Rmpi version 0.5-5 is working very well. Now I have tested "Rmpi 0.5-6". During spawning the Rslaves I get an error: MPI_Error_string: error spawning process > sessionInfo() R version 2.6.0 (2007-10-03) x86_64-unknown-linux-gnu locale:

SLES 9 Service Pack 2 Samba 3.0.14 We are currently experiencing an issue with multiple smbd processes spawning. Do you have any suggestions as how to alleviate this condition or patch this problem? Or is this a configuration issues? Thanks, Mark Naumowicz IT Administrator The Equitable Trust Company 30 St. Clair Ave. West Suite 700 Toronto, Ont. M4V 3A1 416-515-7000 xt365

Hi Sam, Is your PATH set on your user environment variables or on the system? Did you try to remove the entry for R-3.5.2 ? I have tested with a standard install, and I can't reproduce your error. I have the exact same path in my system PATH environment variable for 3.5.3, and nothing for other versions. Sorry I can't be of any more help. Cheers Joris On Mon, Mar 25, 2019 at 4:54 PM

Hi, We're running Samba (3.0.28-1.el5_2.1) on a Redhat (5.2) server using winbind to authenticate against a Windows AD. This all worked fine for a while. But now we have the problem that (some) users coming from Linux clients cause an excessive amount of smbd processes. We had 1 user who had more than 1700 smbd processes all coming from the same client. While on the client side there

Hello, Does anyone have problem with spawning smbd daemon (own by root)? I thought there should be only one smbd daemon running that is owned by root and any other smbd should be owned by users who is using Samba services. Description of my system: Samba-2.0.0 on Compac Proliant x86 running Solaris 2.6 -- --------------------------------------------------- Sunny Hwang Guzman

Hi all, I am noticing some strange behaviour so I am bringing to this list. In the past when I have submitted bugs to bugzilla, I have come here first for confirmation/advice. Hopefully this is appropriate. Upgrading from R 3.5.2 to R 3.5.3 seems to have elicited some strange behaviour on my Windows machine. R seems to have trouble spawning a new process on my machine. You can noticing with all

While we were trying out a new capistrano setup tonight we noticed that the spawner would alternately spawn fcgi processes, then the next time it would kill them, then create, then kill, etc... >From everything I can see/read/know, spawn-fcgi should not affect running processes, right? Anyone else see this weird behavior? For now we are using the ''check the port before

I''ve ran into quiet an annoying problem: I have a Capistrano task that is supposed to run a shell script. The script restarts a rails application by first killing all active fcgi processes and then spawning new ones again. The shell script works fine when executed locally on the server but running this in a Capistrano task will simply not work. The task is simple: desc

Did you TV/Radio broke?? ;-) This really smells like some malware/cryptoware. Seen this ones on a network, and that was a cypto trying to write to shares. And they to that really really fast. Increast the samba debug logs and track if this is client related. That where i would start. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at

Hi! I''ve just a created a really simple rails scheduled worker for backgroundrb to start playing with : class SessionCleanerWorker < BackgrounDRb::Worker::RailsBase def do_work(args) logger.info "SessionCleaner> started" CGI::Session::ActiveRecordStore::Session.destroy_all( [''updated_at <?'', 120.minutes.ago] )

---------- Forwarded message ---------- From: Jim Ballantine <j.ballantine at gmail.com> Date: Tue, Aug 30, 2016 at 7:16 AM Subject: spawning smbd's To: samba at lists.samba.org 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 off. A

Hi all, Sometimes I'll find myself "ctrl-c"-ing like a madman to kill some code that's parallelized via foreach/doMC when I realized that I just set my cpu off to do something boneheaded, and it will keep doing that thing for a while. In these situations, since I interrupted its normal execution, foreach/doMC doesn't "clean up" after itself by killing the

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 off. A couple of us have spent several days trying to determine the reason, but as of now have not found the reason. The top of the smb.conf is: #======================= Global Settings

hi, i have a app which has a spiky activity, there a large period of inactivity between request. With phusion-passenger after a period of inactivity the process is killed, and when the app is respawned the ''show status'' queries take more time than the actual sql themself. I know that ActiveRecord makes the ''show status'' query once on spawning the server, but is

On 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

I am having a problem with my Samba machine, here are the details. The machine in question is running FreeBSD 4.5-RELEASE on a Dual PIII/XEON 550. I downloaded the source for Samba-2.2.3a and compiled without a hitch. I also setup SWAT to run through an stunnel(ssl) pipe. SWAT configuration of Samba worked great, but if I start the daemons(smbd & nmbd) from SWAT, smbd seems to keep creating

Hi, I am using rsync 3.0.4 on a WinXP machine (with CygWin) to synchronize my files to a RedHat Linux server. Everything is working perfectly, but there is one thing I do not understand. Apparently there is a difference in pushing and pulling files with rsync. When I push my files to the server with this command, I see one rsync process on my WinXP machine, just as expected rsync -rlt -e

All, I'm running the latest stable version of SerNet-Samba on a Debian Sarge box (I switched from the traditional Samba package for certain reasons which I won't delve into here), but I've come across a serious issue. Every day, the Samba processes become so numerous that the server begins acting really flaky. That is to say, there are so many smbd -D processes that the server