- **status**: unassigned --> wontfix
- **assigned_to**: Mathi Naickan
- **Milestone**: future --> never
- **Comment**:
Currently the three variables, node_id, component_name, comp_err_source are all
relevant to the components. It would be helpful for applications to know these
values. Also, applications have a means to negate inherting these variables
from within their instantiation scripts. Closing this for now.
---
** [tickets:#327] amf: OpenSAF environment variables inherited by AMF started
processes**
**Status:** wontfix
**Milestone:** never
**Labels:** 4.2FC
**Created:** Fri May 24, 2013 09:37 AM UTC by Praveen
**Last Updated:** Wed Jul 15, 2015 02:36 PM UTC
**Owner:** Mathi Naickan
Migrated from http://devel.opensaf.org/ticket/2244.
The environment variables for AMF started processes needs to be cleaned up.
This is clearly visible from doing
a "env > /tmp/somecomp.env" in a instantiate script.
The question is what are the default env vars for a process? Not clearly
specified by any standard, found this:
http://www.gnu.org/s/hello/manual/libc/Standard-Environment.html#Standard-Environment
---
Sent from sourceforge.net because [email protected] is
subscribed to https://sourceforge.net/p/opensaf/tickets/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/opensaf/admin/tickets/options. Or, if this is a
mailing list, you can unsubscribe from the mailing list.
------------------------------------------------------------------------------
_______________________________________________
Opensaf-tickets mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
