On Mon, Aug 26, 2002 at 04:30:19PM -0400, Brian T. Schellenberger wrote:
> | Mine's a laptop with APM enabled (BIOS + kernel).
>
> But on the other hand mine's a laptop with APM and it doesn't have the
> problem. Then again, my kernel is vintage July 19.
For people seeing this problem with lap
subscribe freebsd-hackers
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
On Tue, Sep 17, 2002 at 05:22:15PM +0700, "Evgueni V. Gavrilov" <[EMAIL PROTECTED]>
wrote:
> Greg Lane wrote:
>
> >Can anyone tell me if this hardware or a real bug? Is there anything
> >else I could supply which would help in understanding the problem?
> take a look at http://www.freebsd.org/cg
Ok, any of you guys have a copy of the standards documents that
describe the sem_* API?
I have a question...
What are the semantics of the sem_init when pshared is set to true?
Like, if the process that created the semaphore exits, then what?
Is it only valid for the life of the process that d
Alfred Perlstein wrote:
> Ok, any of you guys have a copy of the standards documents that
> describe the sem_* API?
>
> I have a question...
>
> What are the semantics of the sem_init when pshared is set to true?
The sem_init() function is used to initialise the unnamed
semaphor
On Wed, 18 Sep 2002, Alfred Perlstein wrote:
>
> Ok, any of you guys have a copy of the standards documents that
> describe the sem_* API?
>
> I have a question...
>
> What are the semantics of the sem_init when pshared is set to true?
>
> Like, if the process that created the semaphore exits
On Wed, 18 Sep 2002, Terry Lambert wrote:
> Alfred Perlstein wrote:
> > Ok, any of you guys have a copy of the standards documents that
> > describe the sem_* API?
> >
> > I have a question...
> >
> > What are the semantics of the sem_init when pshared is set to true?
>
> The sem_init() f
* Daniel Eischen <[EMAIL PROTECTED]> [020918 18:40] wrote:
> On Wed, 18 Sep 2002, Alfred Perlstein wrote:
>
> >
> > Ok, any of you guys have a copy of the standards documents that
> > describe the sem_* API?
> >
> > I have a question...
> >
> > What are the semantics of the sem_init when pshar
On Wed, 18 Sep 2002, Alfred Perlstein wrote:
> * Daniel Eischen <[EMAIL PROTECTED]> [020918 18:40] wrote:
> > On Wed, 18 Sep 2002, Alfred Perlstein wrote:
> >
> > >
> > > Ok, any of you guys have a copy of the standards documents that
> > > describe the sem_* API?
> > >
> > > I have a question
* Daniel Eischen <[EMAIL PROTECTED]> [020918 19:16] wrote:
>
> Yes, but it doesn't change what the spec says above. It's
> implying that any process can perform sem_destroy() on it and
> the spec also says for sem_init() that "This semaphore shall
> remain usable until the semaphore is destroyed
Daniel Eischen wrote:
> > The sem_init() function is used to initialise the unnamed
^^^
> > semaphore referred to by sem. The value of the initialised
^
> > If the pshared argument has a non-zero v
Alfred Perlstein wrote:
> now here's the problem, one can basically stick a sem_t into a shared
> memory location, then one can share it amongst processes (provided
> pshared was set). However there's no requirement that these other
> processes do any form of "open" on the sem_t, hence I really h
Daniel Eischen wrote:
> Yes, but it doesn't change what the spec says above. It's
> implying that any process can perform sem_destroy() on it and
> the spec also says for sem_init() that "This semaphore shall
> remain usable until the semaphore is destroyed.".
The key point is "that can access".
On Wed, 18 Sep 2002, Terry Lambert wrote:
> Daniel Eischen wrote:
> > > The sem_init() function is used to initialise the unnamed
> ^^^
> > > semaphore referred to by sem. The value of the initialised
>
<
said:
> The semaphore remains active until it is destroyed. If you don't
> want to track its page, can you hook it into ipcrm(1)?
A simple way of implementing process-shared anonymous semaphores,
using the kernel support, is to simply create a temporary semaphore,
and (important part) store
Hi,
can you advice which SYSV kernel options and how should I tweak to make
more room for semaphores and shared memory? They are several of them in
the LINT kernel, should I change all of them, or which?
And the second question: how can I delete unused private shared memory
segments? for example
16 matches
Mail list logo
