mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
* Tracking down semaphore usage/leak
@ 2001-06-26 21:09 Ken Brownfield
  0 siblings, 0 replies; 2+ messages in thread
From: Ken Brownfield @ 2001-06-26 21:09 UTC (permalink / raw)
  To: linux-kernel

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

^ permalink raw reply	[flat|nested] 2+ messages in thread
[parent not found: <no.id>]

end of thread, other threads:[~2001-06-26 22:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-06-26 21:09 Tracking down semaphore usage/leak Ken Brownfield
     [not found] <no.id>
2001-06-26 22:24 ` Ken Brownfield

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®