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

maintain hyperboss master log #131

Open
mikkokotila opened this issue Sep 20, 2017 · 0 comments
Open

maintain hyperboss master log #131

mikkokotila opened this issue Sep 20, 2017 · 0 comments
Assignees

Comments

@mikkokotila
Copy link
Contributor

All the experiment results should go to /var/log/hyperboss.log but we have to make sure that there is also some kind of safety mechanism against that file being over written for example with new install or similar situation. There should be no risk of it growing too big, and if it does, we can think about it more then. For now I guess the key point is that there should be an identifier in addition to the hyperscan outputs in terms of what experiment each sample is related with. So maybe add a human readable "experiment id". Perhaps it's a good idea to require the user to input an experiment name when starting hyperboss, and also have a unique id in form of epoch time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants