Hi, I have a problem with Firebird 2.5, and posted the issue in their mailing
list. They suggested that I have to recompile the kernel to allow more SysV
semaphores. Do you recommend this?
Here's a copy of my mail:
> I recently installed Firebird 2.5 on a FreeBSD, it was running ok
On Tuesday 02 December 2008 04:54:27 Bill Moran wrote:
> In response to "DA Forsyth" <[EMAIL PROTECTED]>:
> > Hiya
> >
> > I recently started (trying) to use sshit to filter the many brute
> > force sshd attacks.
> >
> > However, it has never worked on my box. FreeBSD 7.0 p1.
> >
> > This morning
In response to "DA Forsyth" <[EMAIL PROTECTED]>:
> Hiya
>
> I recently started (trying) to use sshit to filter the many brute
> force sshd attacks.
>
> However, it has never worked on my box. FreeBSD 7.0 p1.
>
> This morning it would only give a message (without exiting)
>Could not create
message (without exiting)
>Could not create semaphore set: No space left on device
> at /usr/local/sbin/sshit line 322
> Every time it gets stopped by CTRL-C it leaves the shared memory
> behind, allocated.
>
> I am going to reboot later and double the number of semaphores
/sshit line 322
Every time it gets stopped by CTRL-C it leaves the shared memory
behind, allocated.
I am going to reboot later and double the number of semaphores (in
loader.conf).
I am running hobbit which uses 8, leaving only 2 free. This may
solve this issue, but I'd appreciate any idea
Damian Wiest wrote:
...
No, it's my fault; I checked things on the wrong system. OpenBSD uses
seminfo, FreeBSD uses ipc.
aa the joy of forking :)
--
Robin Becker
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailm
On Tue, Nov 14, 2006 at 11:56:45PM +, Robin Becker wrote:
[snip]
> thanks very much all very useful info. Someone else recommended looking
> at these options
>
> kern.ipc.semmap=180
> kern.ipc.semmni=160
> kern.ipc.semmns=210
> kern.ipc.semmnu=180
> kern.ipc.semmsl=210
> kern.ipc.semopm=25
hat way anymore.
# sysctl -a | grep seminfo
kern.seminfo.semmni=10# number of semaphore identifiers
kern.seminfo.semmns=60 # number of semaphores in system
kern.seminfo.semmnu=30# number of undo structures in system
kern.seminfo.semmsl=60# max number of semaphores per id
kern.seminfo.sem
On Tue, Nov 14, 2006 at 04:46:52PM -0600, Damian Wiest wrote:
> On Tue, Nov 14, 2006 at 03:22:33PM +, Robin Becker wrote:
> > I'm trying to test a python extension (POSH) that uses semaphores. When
> > testing I get a run time error that indicates it requires too many
&
On Tue, Nov 14, 2006 at 03:22:33PM +, Robin Becker wrote:
> I'm trying to test a python extension (POSH) that uses semaphores. When
> testing I get a run time error that indicates it requires too many
> semaphores. Is it possible to adjust the allowed number of semapho
I'm trying to test a python extension (POSH) that uses semaphores. When testing
I get a run time error that indicates it requires too many semaphores. Is it
possible to adjust the allowed number of semaphores without rebuilding the kernel?
What are the costs of having semaphores ie are
Over the past few days, I had some problems with too few connections
availabe for postgresql. I resolved them for the short term, but when I
tried setting the max_connections for postgresql as high as 64, I
received a message indicating that I had to increase the semaphores
available in the
ot a lot of files like these in
/var/run/:
/var/run/httpd.mm.77920.sem
They look like memory management semaphores of some kind (from mm?). Can I
safely delete these files, prior to staring the httpd daemon? I hate them
cluttering up my /var/run/ dir.
I don't see anything like that, so
> Hi,
Hi!
> I was installing perl 5.8 and it would fails. Lost the error message,
sorry.
> However, running a google search on the error message gave only one
> result suggesting that my system was running out of semaphores. So,
> `ipcs` showed that postgresql was using them
Hi,
I was installing perl 5.8 and it would fails. Lost the error message, sorry.
However, running a google search on the error message gave only one
result suggesting that my system was running out of semaphores. So,
`ipcs` showed that postgresql was using them and so stopping this db allowed
Hello,
I just installed Apache/1.3.28, and now I got a lot of files like these in
/var/run/:
/var/run/httpd.mm.77920.sem
They look like memory management semaphores of some kind (from mm?). Can I
safely delete these files, prior to staring the httpd daemon? I hate them
cluttering up my /var/run
Mark <[EMAIL PROTECTED]> writes:
> I just installed Apache/1.3.28, and now I got a lot of files like these in
> /var/run/:
>
> /var/run/httpd.mm.77920.sem
>
> They look like memory management semaphores of some kind (from mm?). Can I
> safely delete these files,
17 matches
Mail list logo
