jaredpetersen / jaredpetersen/raspilive
Old segment files are not removed when service is stopped and started again
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 148
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Steps to reproduce:
1. Start service
2. Stream for a few moments so some file segments are added to wherever they are configured to go
3. stop service
4. start service
5. stream for a few moments again
Expected result:
orphaned segments are cleaned up
Actual result:
orphaned segments remain
This is a concern for the configuration I currently have, where i setup a system service to execute `raspi-live`, and control when it starts and stops with `cron`. With each stop and start, I'm accumulating orphaned segment files that I will need to clean up manually.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the raspi-live service's startup and shutdown handling, then reproduce the stop/start sequence while watching the configured segment directory. Trace where segment files are created and determine what cleanup should occur when the service restarts. Done means repeated stops and starts no longer leave orphaned segments behind.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, raspberry-pi
- Domain
- backend, embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100