[tickets] [opensaf:tickets] #2459 try-again for opensafd stop

2017-06-28 Thread Rafael Odzakow via Opensaf-tickets
- **status**: review --> fixed
- **Comment**:

commit a051496719a3c862594af17d88b082031dd53b33 (ticket-2459)

base: Try again for opensafd stop [#2459]

Internally opensafd creates a mutex during start/stop to avoid parallel
execution. Makes mutex more robust and add a short retry if mutex is
taken.

















---

** [tickets:#2459] try-again for opensafd stop**

**Status:** fixed
**Milestone:** 5.17.08
**Created:** Thu May 11, 2017 12:42 PM UTC by Rafael Odzakow
**Last Updated:** Tue Jun 13, 2017 08:01 AM UTC
**Owner:** Rafael Odzakow


Today there is no way for SMF (or others) to know when opensafd start is 
completed. Calling stop when a start is ongoing will not stop opensafd so the 
reboot will not shutdown opensafd. Resulting in errors reports from several 
components.

Internally opensafd creates a lock file during start/stop. Internally implement 
a try-again loop that will use the opensafd lockfile.


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets


[tickets] [opensaf:tickets] #2459 try-again for opensafd stop

2017-06-13 Thread Rafael Odzakow via Opensaf-tickets
- **summary**: improve state report for opensafd --> try-again for opensafd stop
- Description has changed:

Diff:



--- old
+++ new
@@ -1,3 +1,3 @@
 Today there is no way for SMF (or others) to know when opensafd start is 
completed. Calling stop when a start is ongoing will not stop opensafd so the 
reboot will not shutdown opensafd. Resulting in errors reports from several 
components.
 
-Internally opensafd creates a lock file during start/stop. To allow SMF and 
others to query the state this ticket will use the opensafd lockfile to report 
the status of start/stop when requested with "opensafd status"
+Internally opensafd creates a lock file during start/stop. Internally 
implement a try-again loop that will use the opensafd lockfile.






---

** [tickets:#2459] try-again for opensafd stop**

**Status:** review
**Milestone:** 5.17.08
**Created:** Thu May 11, 2017 12:42 PM UTC by Rafael Odzakow
**Last Updated:** Mon May 15, 2017 01:56 PM UTC
**Owner:** Rafael Odzakow


Today there is no way for SMF (or others) to know when opensafd start is 
completed. Calling stop when a start is ongoing will not stop opensafd so the 
reboot will not shutdown opensafd. Resulting in errors reports from several 
components.

Internally opensafd creates a lock file during start/stop. Internally implement 
a try-again loop that will use the opensafd lockfile.


---

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.--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
Opensaf-tickets mailing list
Opensaf-tickets@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets