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.

Sign up for GitHub

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

Jump to bottom

Use a good logging mechanism #21

Open
darxtrix opened this issue Jul 12, 2017 · 0 comments
Open

Use a good logging mechanism #21

darxtrix opened this issue Jul 12, 2017 · 0 comments
Labels
good first issue refactoring Code refactoring or project structural changes

Comments

@darxtrix
Copy link
Owner

darxtrix commented Jul 12, 2017 •
edited

I am not able to see the logs in the .ptop.log file.

A better way would be make a directory named .ptop and add separate log files under it. For the sake of preventing memory flooding, we have to have some cycling/cleaning mechanism of log files.

Need to see what are the best practices for usage of logging module.

Observations

  • Current behavior is that only INFO level logs are made to the log file and upon termination/quitting of ptop the log file is erased.
@darxtrix darxtrix added good first issue refactoring Code refactoring or project structural changes and removed priority labels Nov 16, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue refactoring Code refactoring or project structural changes
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@darxtrix