Motion time based traffic
I am using Motion for a few years now, but recently moved my server to a hosting area. This resulted in bandwith problems, so I thought making time-based recording would be a solution. In the FAQ I found the Crontab solution and after edditing the crontab, that should work (I can see log entry's with the commands). At this point I still have bandwith issues. It seems pausing the detection doesn't pause the stream. To be sure I didn't do anything wrong, I manually executed the commands to pause and start, these also indicate that it does what it should do.
So, at this point I am wondering if the pause command does: a. pause motion detection b. pause the stream
If it pauses the motion detection, is there a way to pause the stream?
I have a Linksys wvc54g on mjpeg
user:/var/log # /usr/bin/lwp-request http://localhost:8080/0/detection/pause
Thread 0 Detection paused
<a href=/0/detection><- back</a>
| Motion version:
| ffmpeg version:
| Server OS:
|| Opensuse 10.3
- 09 Dec 2008
What about set webcam_port to 0 ?
- 10 Dec 2008
It is set to 0. are you sure this setting has something to do with it. I thought this was some output port, and the 8080 mentioned in my post is some kind of receive port.
- 10 Dec 2008
webcam_port : stream port ... pause stream out , no stream will be send .
Input : pause detection just stops motion algorithm to process images , you delay get images from OUTSIDE ( i guess you are using a netcam from outside your host , you didn't tell so i thought was a USB or cctv attached to that machine ) :
Set to 7200 seconds ?! 36000 seconds ? ... i think is what you want.
- 11 Dec 2008
Well.. Interesting option, I think I didn't formulate my question well. So I will try to clear some things up.
The camera (netcam indeed) in pointing to the outside. Since it's dark between 18:00 and 7:00 it doesn't make sense to find motion, it takes 10 kb/sec during this time-frame. (does take more during the day, dunno why)
On my server (on a hosting site), I have 100 gb per month.The camera takes exactly 3 gb a day. That would be just enough to get me through the month. Well that is if I don't do anything else with the server....
So basicaly I just don't want motion to run between 18:00 and 7:00. The option used with the crontab looked like a solution for this, but now I think it still keeps the line open, but does not do motion detected on the images.
- 11 Dec 2008
Now your questions is neat as glass , so you have an obvious option, use crontab to stop motion at 18:00 and start at 7:00.
- 12 Dec 2008
Correct, I added these lines to the crontab to achieve this
0 7 * * * /etc/init.d/motion start > /dev/null
0 18 * * * /etc/init.d/motion stop > /dev/null
Might be added to the FAQ to clear up the difference between turn motion detection off (as allready mentioned in the FAQ) and motion off (to reduce bandwith usage)
Thanks for your help