PS: just checked images, and both apps start producing under- and overexposed photos after some time.
I ran some more tests: for one, I installed a resource monitor that allows me to monitor CPU usage while running the app. Second, I tried two more apps – FreeDCam (https://github.com/KillerInk/FreeDcam) and Baba (https://gitlab.com/ravenfeld/baba). When I start taking pictures in auto-repeat mode, CPU usage reaches close to 100% after some time. Exposure still remains remarkably stable during that time, it takes some time at full CPU saturation until symptoms are visible on screen (and even then,...
I don’t see that version on F-Droid yet, any ideas when it will be available?
Exposure in repeat mode sporadically goes haywire
I didn’t set any path at all, and would expect that to give me the hardcoded cron default . Instead, this seems to give me the same PATH I would get in a shell environment. That would imply that, if a variable is not set in the crontab, it is still inherited from the shell. For reproducible tests, all environment variables should be unset first, then cron’s hardcoded defaults should be set, and only after that should any settings in crontab be applied. The possibilities of a cron job are almost unlimited,...
Case in point, I am seeing this on my system. If I type echo $PATH in bash, I get: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games Doing the same in a cron job (and redirecting output) gives me: /usr/bin:/bin I did not examine the exact PATH I would get when running from webmin. However, I ran a script that called ifconfig and a few other system commands, which on my system reside in /sbin. The script works when run from Webmin, as well as when running from...
Case in point, I am seeing this on my system. If I type echo $PATH in bash, I get: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games Doing the same in a cron job (and redirecting output) gives me: /usr/bin:/bin I did not examine the exact PATH I would get when running from webmin. However, I ran a script that called ifconfig and a few other system commands, which on my system reside in /sbin. The script works when run from Webmin, as well as when running from...
If the UI advised users that it may take up to a minute for output to appear (plus, depending on the way it is redirected to the user’s browser, the time it takes for the job itself to complete), they would at least know that this is normal, not a malfunction. So we would need to balance between two use cases: * Run the job without even a minute of delay, at the expense of the environment being different from cron and the job potentially behaving differently * Run the job in a true cron environment...