On Tue, Aug 16, 2005 at 03:10:34PM +0200, Joost Bekkers wrote:
> On Tue, Aug 16, 2005 at 04:51:15PM +0400, Dmitry Agaphonov wrote:
> > Hello,
> >
> >
> > I have user A from group G creating shared memory M with permissions
> > 0060. After this, A fails to attach M due to permission denied.
> > H
On Tue, Aug 16, 2005 at 04:51:15PM +0400, Dmitry Agaphonov wrote:
> Hello,
>
>
> I have user A from group G creating shared memory M with permissions
> 0060. After this, A fails to attach M due to permission denied.
> However, another user B from the same group G successfully attaches M.
> User
On Fri, Aug 27, 2004 at 05:18:50PM +0200, Dmitry Karasik wrote:
> I've been playing with shared memory in jails, and very soon found
> out that one jail's segments are visible (didn't check the accesibility
> thoroughly) in another, which IMO is against the very idea of the jail.
kern/48471
--
On 27 Aug 2004 Dmitry Karasik wrote:
>
> Hi hackers,
>
> I've been playing with shared memory in jails, and very soon found
> out that one jail's segments are visible (didn't check the accesibility
> thoroughly) in another, which IMO is against the very idea of the jail.
> ( The exact problem is
On Friday 29 August 2003 20:31, Lev Walkin wrote:
> zera holladay wrote:
> > When one uses the term "shared memory" while
> > discussing Unix, then what is generally the meaning of
> > that term? I have read that some Unixes have "shared
> > memory" for "shared objects."
> > [...]
>
> Shared memor
zera holladay wrote:
When one uses the term "shared memory" while
discussing Unix, then what is generally the meaning of
that term? I have read that some Unixes have "shared
memory" for "shared objects."
However, I believe the term "shared memory" more
generically refers to user space as oppose
Are your processes all created by fork() or are they unrelated? If they're
all descendants of the same process, take a look at the GNU mm library
(which is loosely based on structure of the mm_malloc library I wrote for my
company but couldn't release).
http://www.engelschall.com/sw/mm/
If they'
From: Peter Pentchev [mailto:[EMAIL PROTECTED]]
Sent: den 8 december 2000 14:00
To: [EMAIL PROTECTED]
Cc: Mikko Tyolajarvi; [EMAIL PROTECTED]
Subject: Re: Shared Memory
On Fri, Dec 08, 2000 at 01:01:16PM +0100, William Carlsson - Teligent
Nordic, AB - Sweden wrote:
> Isn't all kern.* read
On Fri, Dec 08, 2000 at 01:01:16PM +0100, William Carlsson - Teligent Nordic, AB -
Sweden wrote:
> Isn't all kern.* read only?
> Seems like it can't be changed more than it's in theory changeable
>
> Something like the maximum nuber of files and processes, that is suposed to
> be
> soft configur
Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mikko Tyolajarvi
Sent: den 7 december 2000 18:54
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Shared Memory
In local.freebsd.hackers you write:
>Could anyone enlighten me on how to set the amount of
In local.freebsd.hackers you write:
>Could anyone enlighten me on how to set the amount of shared memory?
If you mean the wretched System V IPCs, the parameters are in LINT.
Search for "SHM".
>I'd like that info for FreeBSD 2.2.2, 3.x, 4.x
The parameters only have descriptive comments in 4.2,
Hello,
I too had problems with running out of shared mem segments, so I wrote
my first ever perl script that does something useful for me. I've
attached it to this email and I'll paste it in below too, for
convenience.
I noticed that many (most?) of the shared mem segments in use, when I
was run
On Fri, Sep 08, 2000 at 02:56:10PM +0100, John Toon wrote:
>
> However, it seems strange that you're getting non-attached memory
> segments. Surely it is the job of the kernel to clean up after processes
> (if they're badly programmed and don't do it themselves)? Perhaps one
> program is leaking?
Lance Rocker wrote:
> Hello,
>
> I too had problems with running out of shared mem segments, so I wrote
> my first ever perl script that does something useful for me. I've
> attached it to this email and I'll paste it in below too, for
> convenience.
>
> I noticed that many (most?) of the shar
Clive Lin wrote:
>
> Hm... long time ago I asked google about those SHM* and
> I thought SHMSEG may be the key point. Because SHMSEG stands for
> maximum number of shared segments per process.
Fantastic! You're absolutely correct. Everything is now working
perfectly. My mistake had been to think
Hi,
On Tue, Sep 05, 2000 at 10:30:05AM +0100, John Toon wrote:
> options SEMMNI=100
> options SEMMNS=300
> options SEMUME=100
> options SEMMNU=150
> options SHMMAXPGS=16385
Would you like to try below ?
options SHMALL=4097
options SHMMAX="(
I think that there is an application that is not releasing memory resources
you can check that with ipcs and ipcsrm
cheers
At 11:35 AM 9/5/2000 +0100, Konstantin Chuguev wrote:
>John Toon wrote:
>
> > Hi,
> >
> > I've scoured through the net and the mailing archives, but was unable to
> > find
John Toon wrote:
> Hi,
>
> I've scoured through the net and the mailing archives, but was unable to
> find any satisfactory information on a certain problem I'm suffering at
> the moment.
>
> After getting the dreaded "shmget() failed" error message, I have since
> tried several recompiles of the
don't use shmget if you can. Use mmap'ed files. The SYSV shm interface is
incredibly dumb.
ron
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-hackers" in the body of the message
don't use shmget if you can. Use mmap'ed files. The SYSV shm interface is
incredibly dumb.
ron
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
:I've been learning to program using shared memory and messages. As I write
:and debug, I often have to crash a running process which stalls. Of
:course, there is a problem with my code but that's all part of the
:learning process. The actual problem is that, after a few ctrl-c's, there
:isn't enou
:I've been learning to program using shared memory and messages. As I write
:and debug, I often have to crash a running process which stalls. Of
:course, there is a problem with my code but that's all part of the
:learning process. The actual problem is that, after a few ctrl-c's, there
:isn't eno
22 matches
Mail list logo
