#39 too much logs when hardcutting camera

[eatdirt]

Hi there,
one of our users managed to fill-up his harddrive by hardcutting his camera while running guvcview.

Doing so when guvcview has been started from a terminal indeed produces logs forever at a rate equals to the FPS with V4L2_CORE message saying than the buffer cannot be dequeued. But if guvcview has been started out of a terminal, these logs end up stored in X output logs without the users noticing.

Maybe guvcview could gracefully exit in such situations, or produce some logs for a finite amount of time?

Thanks,

Best,
Chris.

[Paulo Assis]

I think a log counter should be easy enough to implement. I'll try to
set this up before the next release.

Thank you.

Paulo

2017-08-25 8:00 GMT+01:00 eatdirt dirteat@users.sf.net:

---

[tickets:#39] too much logs when hardcutting camera

Status: open
Milestone: next
Created: Fri Aug 25, 2017 07:00 AM UTC by eatdirt
Last Updated: Fri Aug 25, 2017 07:00 AM UTC
Owner: Paulo Assis

Hi there,
one of our users managed to fill-up his harddrive by hardcutting his camera
while running guvcview.

Doing so when guvcview has been started from a terminal indeed produces logs
forever at a rate equals to the FPS with V4L2_CORE message saying than the
buffer cannot be dequeued. But if guvcview has been started out of a
terminal, these logs end up stored in X output logs without the users
noticing.

Maybe guvcview could gracefully exit in such situations, or produce some
logs for a finite amount of time?

Thanks,

Best,
Chris.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/guvcview/tickets/39/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/