On Sun, 4 Jun 2006 21:18:50 -0700
David King [EMAIL PROTECTED] wrote:
I have all of the IPC-related sysctls listed below. I do see that
kern.ipc.shmmni is set to 192, and that kern.ipc.semmni is set to 10.
Are those the maximums? What does MNI mean in those names? Is there a
man page or
I have all of the IPC-related sysctls listed below. I do see that
kern.ipc.shmmni is set to 192, and that kern.ipc.semmni is set to 10.
Are those the maximums? What does MNI mean in those names? Is there a
man page or recommended document that describes what these mean in
detail?
ipcs -M or
David King [EMAIL PROTECTED] wrote:
I'm trying to use sshit.pl from /usr/ports/secrurity/sshit, and I'm
having some trouble with it that I think may be a bug, or a mis-
configuration on my part.
sshit is a Perl program that receives syslog messages (configured in
syslog.conf) of the
I'm trying to use sshit.pl from /usr/ports/secrurity/sshit, and I'm
having some trouble with it that I think may be a bug, or a mis-
configuration on my part. [...]
How about the output from 'ipcs -b'.
Here it is. There looks to be quite a few share memory segments (192)
of size 64k owned by
David King [EMAIL PROTECTED] wrote:
I'm trying to use sshit.pl from /usr/ports/secrurity/sshit, and I'm
having some trouble with it that I think may be a bug, or a mis-
configuration on my part. [...]
How about the output from 'ipcs -b'.
Here it is. There looks to be quite a few share
Here it is. There looks to be quite a few share memory segments (192)
of size 64k owned by root, for a total of 12MB.
Any way to find out who (i.e. what process) owns these?
Yes. Read the man page.
Okay, so the following command line (as well as a manual
verification) produces no results
#
I'm trying to use sshit.pl from /usr/ports/secrurity/sshit, and I'm
having some trouble with it that I think may be a bug, or a mis-
configuration on my part.
sshit is a Perl program that receives syslog messages (configured in
syslog.conf) of the form '/failed .*from (\d+\.\d+\.\d+\.\d+)
