- **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 [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.------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/opensaf-tickets
