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.
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
