similar to: smbd running multiple times

Hello List, how much run should i give xen0 if the only service that runs is sshd ? ~# free              total       used       free     shared    buffers     cached Mem:        127032     124952       2080          0       7776      89688 -/+ buffers/cache:      27488      99544 Swap:      1048816          0    1048816 Tasks:  33 total,   2 running,  31 sleeping,   0 stopped,   0 zombie

Should I submit this as a proper bug, or will someone look at it? Basically, between 4.7-REL and 4.8-REL ssh was upgraded and now exhibits the following bug. If you connect with protocol v1 you get three ssh processes, one of which never dies, even after the ssh session has been closed. % ps aux | grep ssh root 219 0.0 0.0 4076 0 ?? IW - 0:00.00 sshd: paul [priv root

>> I'm not sure that I follow. The qmtest stuff isn't working on Zion >> because (I believe) of an upgrade that happened on the machine (the >> qmtest >> binary doesn't work anymore?). Are you seeing a problem on freebsd where >> the feature tests go into a loop? If so, can you provide us with more >> information? >> make, ~ > ps -xu

A typo in test/Makefile was the trigger for this problem: http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/ 020216.html John, can you please look into this bug some more and add some error checking to the llvm-specific qmtest python modules to make this error less severe? Thanks! -Brian On Nov 3, 2004, at 10:35 AM, Brian Gaeke wrote: > > I think there is a very

I think there is a very similar situation with the PowerPC/Mac OS X nightly tests. Over each of the past few nights, something has been filling up the process table, causing me to be unable to log in. The nightly tester wrote out regression test and feature test logs featuring hundreds of "Resource temporarily unavailable" errors from fork(), so I assume it's the qmtest

On Thu, 26 Feb 2015 22:45:02 +0000 Rowland Penny <rowlandpenny at googlemail.com> wrote: > > Just what do you mean by 'allow no connections' ?? where from ? how? ivory:~ wynkoop$ smbclient -L prd2 Receiving SMB: Server stopped responding protocol negotiation failed ivory:~ wynkoop$ and on the server with the samba-tool built config I have these samba related processes:

Brian Gaeke wrote: > > A typo in test/Makefile was the trigger for this problem: > > http://mail.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20041101/ > 020216.html > > John, can you please look into this bug some more and add some error > checking to the llvm-specific qmtest python modules to make this error > less severe? Does the fork bomb occur in the

Hello, I see that incase of command execution: :fork()" is called twice, in sshd. Once to spin off child sshd from parenat and second from child sshd, to execute command. Due to this I see 3 processes being created for each connection viz: 16398 0.0 0.3 1284 892 ?? S 4:33PM 0:00.05 sshd:child 16399 0.0 0.1 320 232 p4 Is+ 4:33PM 0:00.06 -sh -c foo_command 16401 0.0

Hello - I just noticed, that there seems to be a change in the way "process titles" are being set between 2.0.6 and 2.0.7: Behavior of 2.0.6: (ps aux | fgrep dovecot) ------------------ root 30803 0.0 0.0 601540 708 ?? S 1:08AM 0:00.00 dovecot/log _dovecot 30802 0.0 0.0 601544 624 ?? S 1:08AM 0:00.00 dovecot/anvil root 30801 0.0 0.0

I am running centos 4.2 on a P4 3 GIG with 2 GIG ram. This machine has been fine for months. my laptop is fine. X is taking 99 percent of the cpu after some time. All I was doing was editing code. If I killall -9 X it comes back for a while then maxes out again. Any ideas on something to tweek??? THanks, jerry ------------ Tasks: 120 total, 2 running, 118 sleeping, 0 stopped, 0 zombie

Version: dovecot --version: 1.0.0 OS: OS X - 10.4.9 Architecture: G5 Dual/1.8Ghz Had a fairly normal time correction last night: May 9 20:56:56 G518X2 ntpd[219]: time set -1.212733 s Which dovecot duly noted: May 9 20:56:56 G518X2 dovecot: auth(default): Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. This morning all of the dovecot processes are

On 23.8.2019 17.19, Randy Bush via dovecot wrote: > FreeBSD psg.com 11.3-RELEASE-p3 FreeBSD 11.3-RELEASE-p3 > dovecot 2.3.6 (7eab80676) (latest from binary package system) > > symptom: multiple imap4s users complain that they can not fetch mail > > stopping and restarting dovecot is a temporary workaround > > dovenull 3713 0.0 0.0 11036 6816 - I 02:27

FreeBSD psg.com 11.3-RELEASE-p3 FreeBSD 11.3-RELEASE-p3 dovecot 2.3.6 (7eab80676) (latest from binary package system) symptom: multiple imap4s users complain that they can not fetch mail stopping and restarting dovecot is a temporary workaround dovenull 3713 0.0 0.0 11036 6816 - I 02:27 0:00.17 dovecot/imap-login user19 3714 0.0 0.0 9464 4756 - S 02:27

On 4/7/2023 1:13 PM, Yuri wrote: > On 4/7/23 10:08, Bob Rasmussen wrote: >> It depends how you "kill" the SSH server. >> >> If you kill it by sending it a SIGKILL signal, it will NOT notify the >> client, so the client will stay running until the client discovers >> the connection is broken. > > > I run 'kill <pid>' which sends

libswfdec/swfdec_as_object.c | 64 libswfdec/swfdec_file_reference.c | 2 libswfdec/swfdec_load_object.c | 81 libswfdec/swfdec_sprite_movie_as.c | 19 libswfdec/swfdec_system_security.c | 1 test/trace/Makefile.am | 72

Two issues concerning ps commandline options. 1) -v option, cosmetic ! currently the formatting is very unsexy, makes this option rather unusable, you can't easy follow the columns 2) -m option doesn't have precedence over other options forcing the output to be memory sorted. i.e. -u option implies -r (-r = sort by current cpu usage) Now I find the output format of -u very

Samba4 latest on FreeBSD8.1RC2 built and running as a joined DC: 81rc2# pwd /usr/local/samba/sbin 81rc2# ps -ax | grep samba 92436 ?? Ss 0:00.24 ./samba 92437 ?? S 0:00.01 ./samba 92438 ?? I 0:00.04 ./samba 92439 ?? S 0:00.01 ./samba 92440 ?? S 0:00.00 ./samba 92441 ?? S 0:00.00 ./samba 92442 ?? S 0:00.00 ./samba 92443 ?? S 0:00.01 ./samba

Please include the following to bug ID: 26222 at: http://bugs.samba.org/?findid=26222 More checking shows that closing a search window on Windows in the middle of it's search doesn't stop the SMB activity. Network utilization remains high, and it seems as if the server is stuck searching. In an attempt to verify, I created a share on Win2k, and followed the same procedure: Server:

Hello to all, I compiled the source of smbd4wins on a suse 10.2 machine successful. On the same machine there is a samba server ver. 3.0.31. The wins is working but after a couple of days it has a high cpu load which is steadily growing and then the system hangs and I need to restart it: top - 15:11:15 up 6 days, 7:07, 2 users, load average: 0.20, 0.25, 0.29 Tasks: 311 total, 2 running,

http://bugzilla.mindrot.org/show_bug.cgi?id=1374 Summary: sshd -D produces zombies if authentication is interrupted Product: Portable OpenSSH Version: 4.7p1 Platform: All OS/Version: FreeBSD Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: bitbucket at