Skip to content

Conversation

@murrown
Copy link
Member

@murrown murrown commented Aug 24, 2015

This command takes the filename of the most recent log file as an argument. It keeps the name of the previous log file in a stop file, so it will read what remains of the previous log file before starting on the newest log file.

@akeym
Copy link
Member

akeym commented Aug 27, 2015

pytz... i don't think that's in the requirements file?

@murrown
Copy link
Member Author

murrown commented Aug 27, 2015

Hmm... I thought it was part of the standard library since it's on all of my computers but I guess not.

@akeym
Copy link
Member

akeym commented Sep 15, 2015

Okay, its been so long since we last talked about this that I forgot how this was supposed to work. It appears that updating the file date causes it to start over. This has to do with the symlink only changing every day right? So we keep reading more of the file until the date changes?

@akeym
Copy link
Member

akeym commented Sep 15, 2015

Yeah, that seems to be the deal. I'm going to get a test running... @murrown maybe prepare a PR or add to this PR the last-seen value back to the UI?

@murrown
Copy link
Member Author

murrown commented Sep 16, 2015

Alright, I'll add it to this pull request.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants