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

doc: FAQ entries about log file #1644

Merged
merged 7 commits into from
Feb 15, 2024
Merged

Conversation

buhtz
Copy link
Member

@buhtz buhtz commented Feb 14, 2024

Add two FAQ entries about the location of log files and how to read them.

Related to #1643

@buhtz buhtz mentioned this pull request Feb 14, 2024
FAQ.md Outdated Show resolved Hide resolved
@buhtz
Copy link
Member Author

buhtz commented Feb 15, 2024

Thanks for review. I'll wait for feedback from @ceperman .

@buhtz buhtz self-assigned this Feb 15, 2024
@buhtz buhtz added the Feedback needs user response, may be closed after timeout without a response label Feb 15, 2024
@buhtz buhtz added this to the Upcoming release (1.5.0) milestone Feb 15, 2024
@ceperman
Copy link

Yes, that's great thanks. It looks like syslog contains the info I was asking for, and the faq describes how to find it - for me:
journalctl --grep backintime

It also shows, by absence of logging, when BIT didn't run when one might have expected it to, which is also very helpful. I thought BIT used anacron (old info in internet says it does) but that's obviously changed and the current docs makes it clear that it doesn't, so if the computer is switched off at the scheduled time, the backup doesn't get taken. My problem. RTFM!

@buhtz
Copy link
Member Author

buhtz commented Feb 15, 2024

Thanks for your feedback. Please let us know if you see more aspects for improvement in the docs. Don't hasitate to open multiple issues for this or sending an email to the mailing list.

I thought BIT used anacron (old info in internet says it does) but that's obviously changed

Myself I am not sure if it was that way in that past. But currently BIT try to Imitate an anacron-like behavior. Maybe that is the reason why some people think anacron is involved. How the scheduling works is described here in the (quite out-dated) docs. The scheduling option "Repeatedly (anacron)" is not anacron but just a simple cronjob starting BIT every 15 minutes.

It is on my list to improve that scheduling section to make it more clear to users what is going on. See #1449

@buhtz buhtz merged commit 6c2c13a into bit-team:dev Feb 15, 2024
1 check passed
@buhtz buhtz deleted the doc/1643faq_about_logs branch February 15, 2024 12:39
@ceperman
Copy link

Thanks. I had not noticed that "Repeatedly (anacron)" was a scheduling option - I'd assumed it was a checkbox option that's missing from my oldish Linux Mint distribution version. Again RTFM!

@buhtz buhtz removed the Feedback needs user response, may be closed after timeout without a response label Feb 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants