- **status**: unassigned --> fixed
---
** [tickets:#2402] base: "hardening" use of lockfile in opensafd**
**Status:** fixed
**Milestone:** 5.2.RC2
**Created:** Wed Mar 29, 2017 10:40 AM UTC by Hans Nordebäck
**Last Updated:** Mon Apr 24, 2017 01:37 PM UTC
**Owner:** Hans Nordebäck
- **status**: fixed --> unassigned
- **Blocker**: --> False
---
** [tickets:#2402] base: "hardening" use of lockfile in opensafd**
**Status:** unassigned
**Milestone:** 5.2.RC2
**Created:** Wed Mar 29, 2017 10:40 AM UTC by Hans Nordebäck
**Last Updated:** Mon Apr 24, 2017 01:37 PM UTC
I have seen a issue with the lockfile. Here are some parts from the system log:
21:59:15 SC-1 opensafd: Starting OpenSAF Services(5.2.0 -
8767:c1cc2a915e72:default) (Using TCP)
- Reboot command is issued from SC-2:
21:59:16 SC-2 osafsmfd[599]: NO STEP: Reboot node for removal
- **status**: review --> fixed
- **Comment**:
changeset: 8739:811a5c573665
user:Hans Nordeback
date:Thu Mar 30 12:09:26 2017 +0200
summary: base: "hardening" use of lockfile in opensafd [#2402]
---
** [tickets:#2402] base: "hardening" use
---
** [tickets:#2402] base: "hardening" use of lockfile in opensafd**
**Status:** review
**Milestone:** 5.2.RC2
**Created:** Wed Mar 29, 2017 10:40 AM UTC by Hans Nordebäck
**Last Updated:** Wed Mar 29, 2017 10:40 AM UTC
**Owner:** Hans Nordebäck
"hardening" use of lockfile in opensafd