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

Old segment files are not removed when service is stopped and started again #39

Open
johnwcassidy opened this issue May 15, 2020 · 1 comment

Comments

@johnwcassidy
Copy link
Contributor

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.

Screen Shot 2020-05-14 at 11 39 24 PM

@jaredpetersen
Copy link
Owner

Yeah, we'd have to look at refactoring how these get cleaned up. Right now, FFMpeg handles that completely.

An easy fix would just be that raspi-live removes everything in the directory on startup so that it starts with a clean slate.

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