Thank you for your explanation. Since threads are still at "dev"-status (and btw slow on creation in perl), I'll switch to forking processes. Those hopefully work the same on different kernels/implementations. Do they?
You mentioned that memory is beeing shared when using threads. I could sucessfully change shared memory data as a non-superuser (with this threads-behaviour). But if you now use IPC::Shareable, you are able to set permissions for the shared memory between processes. Is the sharing between processes or threads on the same level (on Linux)? So you possibly could change permissions for thread shared memory as well? I'm just curious about shared memory, because it seems to me to be a good IPC tool.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|