Path: utzoo!mnetor!frank
From: frank@mnetor.UUCP (Frank Kolnick)
Newsgroups: comp.os.misc
Subject: Re: QNX shared buffer.
Message-ID: <5554@mnetor.UUCP>
Date: 10 Aug 90 00:23:45 GMT
References: <1990Aug7.105617.20133@ifi.uio.no>
Reply-To: frank@mnetor.UUCP (Frank Kolnick)
Organization: Motorola Canada Ltd., Computer X division, Toronto, Ontario, Canada
Lines: 40

In article <1990Aug7.105617.20133@ifi.uio.no> gisle@ifi.uio.no (Gisle Hannemyr) writes:
)I hope this is the appropriate newsgroup for questions about QNX.

	seems to be :-)

)I want to allocate a buffer that shall be used to share information between
)several processes running on the same CPU.  Each process will run for a
)short time, but I want the common buffer to exist "forever".

	as long as the tasks are all on the same node, you can allocate
	a segment, make it read/write, and give access to the relevant
	tasks. the segment belongs to the originating task, so that task
	will have to stay around.

	(described adequately in the manuals, much better in my book :-)
	which has coded examples and nice diagrams.
    available from Qering Software in Switzerland:  tel. 064-51 74 75,
	fax 064-51 75 10 )

)What I really want to do, is to write a program that mallocs some memory,
)associate a name with it (so other processes can read it), and then dies,
)leaving the malloced memory allocated and available for reads and writes
)from other processes that knows its name.

	you can't name the segment; perhaps you want a memory-mgt. task?
	(which can have a globally registered name)

)2) How do I leave a program like that sleeping _forever_?  Preferably
)   not using any cycles.

	'sleep' would do it. so would 'receive' (assuming no one sends
	it messages). depends on what you want the task to do (or not do).
	a sleeping task (like a rolling stone) consumes no cycles.	
	am I misunderstanding your question?


-- 
Frank Kolnick,
Basis Computer Systems Inc.
UUCP: {allegra, linus}!utzoo!mnetor!frank