Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

POSIX shared memory usage #26

Closed
GoogleCodeExporter opened this issue Jun 11, 2015 · 1 comment
Closed

POSIX shared memory usage #26

GoogleCodeExporter opened this issue Jun 11, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Feature description:

libnetconf curretnly uses System V shared memory. Despite this is the most 
common type of shared memory mechanism, configure should detect that it is 
available and there should be possibility to switch to the POSIX shared memory. 
Consider a complete switch to the POSIX shared memory.

In general, utilization of the shared memory in libnetconf should be reviewed 
to allow using libnetconf in multiple independent applications running on the 
system. Currently, all applications using libnetconf are always connected.

Original issue reported on code.google.com by rkre...@cesnet.cz on 21 Jan 2014 at 8:10

@GoogleCodeExporter
Copy link
Author

This issue was closed by revision 97d46b7f78cb.

Original comment by rkre...@cesnet.cz on 19 May 2015 at 11:35

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant