From: Ken Brownfield <brownfld@irridia.com>
To: linux-kernel@vger.kernel.org
Subject: Tracking down semaphore usage/leak
Date: Tue, 26 Jun 2001 14:09:16 -0700 [thread overview]
Message-ID: <200106262109.QAA15955@asooo.flowerfire.com> (raw)
With RedHat's new Samba 2.0.10 RPM (the one to patch the latest
vulnerability) they seem to have sniffed enough glue to start using SysV
IPC semaphores which apparently leak until SEM??? are reached. semget()
is returning "No space left on device", and disk/inodes/memory are all
fine.
Anyway, could someone give me a very quick rundown of the options for
tracking/force-freeing semaphores, or how to determine from proc, if
possible, what the current semaphore allocation status is? Or did RH
slay a machine I really don't want to reboot? I've restarted all
semaphore-using processes to no avail, but even so the SEM??? limits are
far above the normal needs of this machine.
Thanks much. Searched the archives/Google/FAQ/semaphore docs; sorry if
it's been covered. I'll summarize if folks want to hit me on or off the
list.
--
Ken.
brownfld@irridia.com
next reply other threads:[~2001-06-26 21:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-26 21:09 Ken Brownfield [this message]
[not found] <no.id>
2001-06-26 22:24 ` Ken Brownfield
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200106262109.QAA15955@asooo.flowerfire.com \
--to=brownfld@irridia.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®