[tickets] [opensaf:tickets] #2010 IMM: library receives wrong response when a ccb is aborted
- **status**: accepted --> review --- ** [tickets:#2010] IMM: library receives wrong response when a ccb is aborted** **Status:** review **Milestone:** 5.0.2 **Created:** Thu Sep 08, 2016 07:10 AM UTC by Hung Nguyen **Last Updated:** Tue Sep 20, 2016 05:55 PM UTC **Owner:** Hung Nguyen **Attachments:** - [logs.7z](https://sourceforge.net/p/opensaf/tickets/2010/attachment/logs.7z) (6.8 MB; application/octet-stream) When receiving the ccb abort message (D2ND_ABORT_CCB) over fevs, IMMND will abort the message and send response to client if it's the originating node. See immnd_evt_proc_ccb_finalize(). In some cases the client is not in a sync call (i.e. not waiting for response) but IMMND still sends that response to the client. One example is when the OI attaches/deattaches. That may cause the client to receive unexpected response if the client at that time calls an sync IMM api. Details of the problem is explained here http://sequencediagram.org/index.html?initialData=A4QwTgLglgxloDsIAICSBZdBBAUKSs8ISamAcgCJ7jRyIobpU5gBGA9gB7LsBuApmFJMAXFmQwYrALQgOkZFADOyAOb8EgkBH4ATADoIA7gAsNyAPKpk2iCBgmoCVQHpd-W-cfOcORhWkAYlUwfg0APkZKEQoAJkoAfSwAIQsAJQAVBIBhbOTkAApAgEYASj9MLCDWABsAV35I8goxeIocvKSABS6AGQBNQsDY8pYObj5BYWioimRgMHYYfiUlFYkpWXkUAFslVWQAM0Wd4QpDYl1kNYRdFVClYHYENeQIdh4wKFUnbScDhDsdyGNb8RQ7HboIH8GoJSSsLDbAqjWZBUK6JrYESUWJYBKMBIAUTSaXSCViyCMUAgJmQADEsKheoT2hYusSsBlUBYyEMAMylQwAKhFGUcKmUbzMEmeawAjg0EMseIdkCVfGwuDwBEJGFgRHrkKFllABCoaWCHk8XmDLlKnABrc0mbSUkDOy0ra1rQyHdhCYYAGmQrDqKHsEDqIBqNQAnooIAByFQAKzqSnDMptCo0yvYqpKhkMhuN-FN6wtlMWziNXtlYNDKF0UF0CETKBgYHdtLMoUMrH4MBA6bBFh2uQRwGAceRNkk-GAEBUOLxBOJpLS5I1421Uz1IjH2SkWCnM9KtcjYBe9MZzNZXUMJ+nsD+zyz0AQDRUVJplh2WF0HYnAsIxNDAOlfhqKAAC9+GRXw9WqepGlmVpEiwCh0AsBI6VQMgsF6VAAC1CSGAAWUZNQmHVphaWZkEBIxrg0O4pU9R56yOf01ViBDmjRPRMX1Fd8UwIkSTJCkf1pBkmRZBI2Q5LkeX5QUEBFIUxUlSVKytTi-QDXixi1SZdUqA1KhsVQQCcWsTTNGxAQtIQjGrA49JtIsEFQDsuyUMxnR0qAdgbQdh1eMcAKAhAQLAiCEGjGC4LU3R2BWNtw3n RdkBEtcJM3XigA ~~~ 09:45:58 SC-2-2 osafimmnd[3918]: NO ERR_TRY_AGAIN: ccb 1266 is active on object CmwSwMswMId=1 of class CmwSwMSwM. Can not add class implementer 09:45:58 SC-2-2 osafimmnd[3918]: NO Trying to abort ccb 1266 to allow implementer CoreMwSwM to protect class CmwSwMSwM 09:45:58 SC-2-2 osafimmnd[3918]: NO implementer for class 'CmwIspConfig' is CmwIsp => class extent is safe. 09:45:58 SC-2-2 osafimmnd[3918]: NO Implementer disconnected 169 <0, 2010f> (@ClusMonEE) 09:45:58 SC-2-2 osafimmnd[3918]: NO Ccb 1266 ABORTED (CoreMwEcimSwMBackgroundThread) 09:45:58 SC-2-2 ecimswm: ImmUtils::doImmOperations:saImmOmCcbApply failed SaAisErrorT=21 09:45:58 SC-2-2 ecimswm: EcimSwmAsyncImmOperation::main() failed with rc = 21(SA_AIS_ERR_FAILED_OPERATION) 09:45:58 SC-2-2 ecimswm: imma_om_api.c:8769: saImmOmAdminOwnerFinalize: Assertion 'out_evt->info.imma.type == IMMA_EVT_ND2A_IMM_ERROR' failed. 09:45:58 SC-2-2 osafimmnd[3918]: NO Implementer connected: 173 (ClusMonEE) <0, 2010f> 09:45:58 SC-2-2 osafimmnd[3918]: WA >>s_info->to_svc == 0<< reply context destroyed before this reply could be made 09:45:58 SC-2-2 osafimmnd[3918]: WA Failed to send response to agent/client over MDS ~~~ Attached is syslog and IMM traces --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2053 clm: add support for cluster reboot
- **summary**: amf: add support for cluster reboot --> clm: add support for cluster reboot - **status**: review --> accepted - **Comment**: Add support for cluster reboot via command immadm -a safClmService -o 100 safClmService. Clmsv to send reboot request message to clm nodeagent. Each clm node agent will call shutdown –r. --- ** [tickets:#2053] clm: add support for cluster reboot** **Status:** accepted **Milestone:** 5.2.FC **Created:** Tue Sep 20, 2016 12:54 PM UTC by Hans Nordebäck **Last Updated:** Wed Sep 21, 2016 01:36 PM UTC **Owner:** Hans Nordebäck Add support for cluster reboot via command immadm -a safAmfService -o 100 safAmfService --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1800 AMF : Proxied should be brought down initially during NG lock-in admin op
- **status**: unassigned --> assigned - **assigned_to**: Praveen --- ** [tickets:#1800] AMF : Proxied should be brought down initially during NG lock-in admin op** **Status:** assigned **Milestone:** 5.0.2 **Created:** Sat Apr 30, 2016 07:50 AM UTC by Srikanth R **Last Updated:** Tue Sep 20, 2016 05:45 PM UTC **Owner:** Praveen Changeset : 7436 Setup : 2n Red model with proxy and proxied SU hosted on same node. During lock-in operation of node group, initially proxied SU should be brought down ( .i.e, component termination callback should be sent for proxied ) and later proxy SU should be brought down. But in the current implementation, proxy SU is brought down initially and later proxied SU is tried to be brought down , which got failed as there is no proxy. 436 05:30:00 01/01/1970 NO safApp=safAmfService "Admin op "LOCK_INSTANTIATION" initiated for 'safAmfNodeGroup=SCs,safAmfCluster=myAmfCluster', invocation: 300647710721" 437 05:30:00 01/01/1970 NO safApp=safAmfService "safAmfNodeGroup=SCs,safAmfCluster=myAmfCluster AdmState LOCKED => LOCKED_INSTANTIATION" 438 05:30:00 01/01/1970 NO safApp=safAmfService "safAmfNode=SC-1,safAmfCluster=myAmfCluster AdmState LOCKED => LOCKED_INSTANTIATION" 439 05:30:00 01/01/1970 NO safApp=safAmfService "safAmfNode=SC-2,safAmfCluster=myAmfCluster AdmState LOCKED => LOCKED_INSTANTIATION" 440 05:30:00 01/01/1970 NO safApp=safAmfService "safComp=proxied,safSu=PROXIED_SU1_2N,safSg=PROXIED_SG_2N,safApp=PROXIED_2N ProxyStatus is now UNPROXIED" 441 05:30:00 01/01/1970 NO safApp=safAmfService "safSu=PROXY_SU1_2N,safSg=PROXY_SG_2N,safApp=PROXY_2N PresenceState TERMINATING => UNINSTANTIATED" 442 05:30:00 01/01/1970 NO safApp=safAmfService "safSu=PROXIED_SU1_2N,safSg=PROXIED_SG_2N,safApp=PROXIED_2N PresenceState TERMINATING => UNINSTANTIATED" 443 05:30:00 01/01/1970 NO safApp=safAmfService "safSu=PROXIED_SU1_2N,safSg=PROXIED_SG_2N,safApp=PROXIED_2N OperState ENABLED => DISABLED" 444 05:30:00 01/01/1970 NO safApp=safAmfService "Autorepair not done for 'safSu=PROXIED_SU1_2N,safSg=PROXIED_SG_2N,safApp=PROXIED_2N'" 445 05:30:00 01/01/1970 NO safApp=safAmfService "Admin op done for invocation: 300647710721, result 1" --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2059 AMF: SU struck in terminating state, for failure in component restart
- **status**: unassigned --> assigned - **assigned_to**: Praveen - **Milestone**: 4.7.2 --> 5.0.2 --- ** [tickets:#2059] AMF: SU struck in terminating state, for failure in component restart** **Status:** assigned **Milestone:** 5.0.2 **Created:** Thu Sep 22, 2016 07:05 AM UTC by Srikanth R **Last Updated:** Thu Sep 22, 2016 07:05 AM UTC **Owner:** Praveen **Attachments:** - [2059.tgz](https://sourceforge.net/p/opensaf/tickets/2059/attachment/2059.tgz) (821.7 kB; application/x-compressed-tar) Setup : Changeset : 7997 5.1.FC Setup : 5 node setup with 3 payloads. App : 2N PI Application with SUs hosted on PL-3,PL-4,SC-2. Issue : SU struck in terminating state, for failure in component restart Steps performed : -> Initially brought up the attached AMF configuration and 2 SUs got assigned successfully. -> Now moved the instantiation script on SU1. Note that termination script and instantiation script are different. -> Killed component of SU1. The component went for restart and assignments got removed from SU1 and SU2 & SU3 got active & standby. -> As the instantiation script is not available, SU should be moved to instantiation failed state. But the SU is struck in terminating state. -> Lock operation on SU succeeded, but lock-in operation on SU resulted in SG unstable. 175 12:28:31 09/22/2016 NO safApp=safAmfService "Admin op "LOCK" initiated for 'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN', invocation: 408021893121" 176 12:28:31 09/22/2016 NO safApp=safAmfService "safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN AdmState UNLOCKED => LOCKED" 177 12:28:31 09/22/2016 NO safApp=safAmfService "Admin op done for invocation: 408021893121, result 1" 178 12:28:39 09/22/2016 NO safApp=safAmfService "Admin op "LOCK_INSTANTIATION" initiated for 'safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN', invocation: 412316860417" 179 12:28:39 09/22/2016 NO safApp=safAmfService "Admin op invocation: 412316860417, err: ''safSu=TestApp_SU1,safSg=TestApp_SG1,safApp=TestApp_TwoN' presence state is '4''" 180 12:28:39 09/22/2016 NO safApp=safAmfService "Admin op done for invocation: 412316860417, result 6" --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2050 PLM: update PR doc to address new virtualization configuration
- **status**: review --> fixed --- ** [tickets:#2050] PLM: update PR doc to address new virtualization configuration** **Status:** fixed **Milestone:** 5.1.0 **Created:** Mon Sep 19, 2016 01:58 PM UTC by Alex Jones **Last Updated:** Tue Sep 20, 2016 05:33 PM UTC **Owner:** Alex Jones This ticket is for updating the PLM PR doc to reflect virtualization enhancement in 5.1 --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2065 amf: support for SA_AMF_CLUSTER_RESET recommended recovery
--- ** [tickets:#2065] amf: support for SA_AMF_CLUSTER_RESET recommended recovery** **Status:** unassigned **Milestone:** 5.2.FC **Created:** Fri Sep 23, 2016 11:54 AM UTC by Mathi Naickan **Last Updated:** Fri Sep 23, 2016 11:54 AM UTC **Owner:** nobody Support for the SA_AMF_CLUSTER_RESET = 7, Recommended recovery - both as configuration and for error reporting via saAmfComponentErrorReport --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2066 smf: In admin operation handling a not needed delay may be executed
--- ** [tickets:#2066] smf: In admin operation handling a not needed delay may be executed** **Status:** unassigned **Milestone:** 5.1.1 **Created:** Fri Sep 23, 2016 11:54 AM UTC by elunlen **Last Updated:** Fri Sep 23, 2016 11:54 AM UTC **Owner:** nobody In method nodeGroupAdminOperation() a try again loop will do an not needed delay in some cases. Refactor this loop --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] Re: #2053 clm: add support for cluster reboot
As per CLM information model, This operation should be introduced as an admin operation on the object of SaClmCluster class. i.e. immadm -o safCluster=myClmCluster B.T.W i just created a ticket in AMF https://sourceforge.net/p/opensaf/tickets/2065/ --- ** [tickets:#2053] clm: add support for cluster reboot** **Status:** accepted **Milestone:** 5.2.FC **Created:** Tue Sep 20, 2016 12:54 PM UTC by Hans Nordebäck **Last Updated:** Fri Sep 23, 2016 08:20 AM UTC **Owner:** Hans Nordebäck Add support for cluster reboot via command immadm -a safAmfService -o 100 safAmfService --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2017 Update the SMF PR document with information about faster upgrade
- **status**: accepted --> fixed - **Comment**: changeset: 197:bb8308b1b865 tag: tip user:Rafael Odzakow date:Fri Sep 23 14:49:20 2016 +0200 summary: smf: update PR with information about faster upgrade [#2017] Node ID bb8308b1b865b5dbdaccae90f7ad2684e0918fc5 Parent 22151aff279d6fbc4a7251613ba1a63738dc4fe4 --- ** [tickets:#2017] Update the SMF PR document with information about faster upgrade** **Status:** fixed **Milestone:** 5.1.0 **Created:** Fri Sep 09, 2016 12:22 PM UTC by elunlen **Last Updated:** Wed Sep 21, 2016 12:35 PM UTC **Owner:** elunlen Update the SMF PR document with information about: * Balanced In Service Upgrade (BISU) [#1685] * Parallel swBundle removal and installation [#1633] * NG lock and unlock in single step upgrade [#1634] --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2033 AMF: Update documentation for admin op continuation after headless
- **status**: review --> fixed - **assigned_to**: Minh Hon Chau --> nobody --- ** [tickets:#2033] AMF: Update documentation for admin op continuation after headless** **Status:** fixed **Milestone:** 5.1.0 **Created:** Wed Sep 14, 2016 06:09 AM UTC by Minh Hon Chau **Last Updated:** Thu Sep 22, 2016 05:24 AM UTC **Owner:** nobody Need to update README/PR doc for #1987 (fixed) and maybe #1988 (review) --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #2033 AMF: Update documentation for admin op continuation after headless
changeset: 8134:c1ba3c0e157f branch: opensaf-5.1.x tag: tip user:minh-chau date:Fri Sep 23 18:54:22 2016 +1000 summary: AMF: Update README for SC Absence feature [#2033] changeset: 8132:69b250ead8ce user:minh-chau date:Fri Sep 23 18:54:22 2016 +1000 summary: AMF: Update README for SC Absence feature [#2033] --- ** [tickets:#2033] AMF: Update documentation for admin op continuation after headless** **Status:** fixed **Milestone:** 5.1.0 **Created:** Wed Sep 14, 2016 06:09 AM UTC by Minh Hon Chau **Last Updated:** Fri Sep 23, 2016 01:09 PM UTC **Owner:** nobody Need to update README/PR doc for #1987 (fixed) and maybe #1988 (review) --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1859 fm: Add support for STONITH fencing
Doc updates pushed. changeset: 199:6df8c2965315 tag: tip user:mathi.naic...@oracle.com date:Fri Sep 23 19:24:52 2016 +0530 summary: overview: updates related to fencing using stonith[#1859] Can take another stab upon receiving any comments. --- ** [tickets:#1859] fm: Add support for STONITH fencing** **Status:** fixed **Milestone:** 5.1.FC **Created:** Wed Jun 01, 2016 01:49 PM UTC by Hans Nordebäck **Last Updated:** Wed Aug 03, 2016 01:00 PM UTC **Owner:** Hans Nordebäck **Attachments:** - [self_fencing.diff](https://sourceforge.net/p/opensaf/tickets/1859/attachment/self_fencing.diff) (6.1 kB; text/x-patch) Split brain can occur in OpenSAF if either both links between the two controllers are "lost" or one of the controller "live hangs". OpenSAF handles and detects split-brain via FM and uses PLM to fence the other system controller using reboot. PLM only supports target environments running on particular hardware Only a few split-brain cases has been seen and only when running in virtualized environments: 1) Virtual switches problems that makes SCs isolated from each other. 2) Both TIPC links between the SCs are "down/lost", e.g. TIPC tolerance time too low, non-redundant links, other latencies etc. 3) A system controller in a virtual machine is "live hanging" for several seconds, e.g. due to live migration/snapshotting. To be able to do power fencing in a virtualized environment this ticket suggests to use STONITH. When FM detects its peer is not available, both active and standby, in an virtualized environment the active FM system controller will use STONITH to power fence the FM standby system controller. The FM standby system controller will also power fence, but with a delay, the active FM system controller. This will solve the above identified split-brain cases. It will also fit well with the roaming feature. E.g. after power fencing a standby controller a new standby controller will automatically be selected by the roaming feature. In situations where remote fencing is not possible, we could also enhance the criteria for when a node should self-fence. The attached patch self_fencing.diff is a proposal for a mechanism that can detect when a controller node suddenly loses contact with all the other nodes in the cluster, in which case it will assume the fault is local and reboot itself. --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
[tickets] [opensaf:tickets] #1890 Doc : Headless feature documentation
- **status**: accepted --> review --- ** [tickets:#1890] Doc : Headless feature documentation ** **Status:** review **Milestone:** 5.1.0 **Created:** Tue Jun 21, 2016 11:02 AM UTC by Srikanth R **Last Updated:** Wed Sep 21, 2016 11:41 PM UTC **Owner:** Mathi Naickan Version : Opensaf 5.0. GA 1) Documentation about headless feature should be updated in Opensaf_Overview_PR.odt / Opensaf_Extentsions. The documentation should list out services which provide functionality, when the cluster goes headless. 2) The README.HYDRA file in the ntfsv folder should be renamed to README.HEADLESS for uniformity in naming the files across all the folders. 3) CLM folder doesn't have README for the headless feature. 4) The headless files across all folders should have same naming convention. ./osaf/services/saf/amf/README_HEADLESS ./osaf/services/saf/logsv/README-HEADLESS ./osaf/services/saf/cpsv/README.HEADLESS --- Sent from sourceforge.net because opensaf-tickets@lists.sourceforge.net 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 Opensaf-tickets@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
