Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initialize system log mode implementation doesn't match requirement cES1522 #410

Closed
skliper opened this issue Nov 18, 2019 · 6 comments · Fixed by #625
Closed

Initialize system log mode implementation doesn't match requirement cES1522 #410

skliper opened this issue Nov 18, 2019 · 6 comments · Fixed by #625
Assignees
Labels
Milestone

Comments

@skliper
Copy link
Contributor

skliper commented Nov 18, 2019

Is your feature request related to a problem? Please describe.
Requirement cES1522 "Upon a Processor Reset, the cFE shall set the System Log Mode to discard."
Implementation:

/*
** Initialize systemlog to default mode
*/
CFE_ES_ResetDataPtr->SystemLogMode = CFE_PLATFORM_ES_DEFAULT_SYSLOG_MODE;

The build verification test just happens to pass because the sample configuration defaults the mode to discard.

Describe the solution you'd like
Update requirement or implementation.

Describe alternatives you've considered
None

Additional context
None

Requester Info
Jacob Hageman - NASA/GSFC

@jphickey
Copy link
Contributor

Recommend the requirement be reworded to say "Upon a Processor Reset, the cFE shall set the System Log Mode to the platform default"

@skliper
Copy link
Contributor Author

skliper commented Nov 18, 2019

I should have included the rational: "Want to preserve the System Events that may have captured the cause of the processor reset." So intent was to specifically override on a processor reset. Definitely open for discussion...

@jphickey
Copy link
Contributor

jphickey commented Nov 18, 2019

And one can achieve (or fail to achieve) the goal stated in the rationale either way. It is just as easy to lose the syslog information with it set to discard, as the log may have been full already when the event occurred. At the end of the day this is just a system integration issue. Seems pretty cut and dry to me - cfe cannot "enforce" that deployments are correctly configured.

@skliper
Copy link
Contributor Author

skliper commented Nov 18, 2019

It's definitely one for the architects @acudmore @jwilmot. I'd think the vision in mind was for typical use default to overwrite for power on reset, force to discard on processor reset. User setting to discard at power on is certainly their choice to make, for which the discard on processor reset has no effect.

@skliper
Copy link
Contributor Author

skliper commented Feb 10, 2020

Path forward - separate configurable default for power on and processor reset. Default power on to overwrite and processor reset to discard. Requirements will be updated to match (will like req issue to this one). Users can modify however desired, but comes out of the box with the configuration that matches initial intent.

@skliper skliper added this to the 6.8.0 milestone Feb 10, 2020
@skliper
Copy link
Contributor Author

skliper commented Feb 11, 2020

See cES1522 and cES1523 updates in #509

@dmknutsen dmknutsen self-assigned this Apr 9, 2020
dmknutsen added a commit to dmknutsen/cFE that referenced this issue Apr 20, 2020
astrogeco added a commit that referenced this issue Apr 28, 2020
Fix #410, separate SYSLOG configurable defaults for power on and proc…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants