Timeline for Motion goes active (exited) after a few minutes
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 26, 2016 at 20:39 | vote | accept | gloaiza | ||
| May 22, 2016 at 4:35 | comment | added | Mohammad Ali | Don't forget to mark an answer as accepted if it helped you solve your problem, as it will let others know that it is a valid solution | |
| May 18, 2016 at 4:51 | answer | added | Mohammad Ali | timeline score: 0 | |
| May 15, 2016 at 22:27 | comment | added | Kolban | See the following video about starting a program at boot time. youtube.com/watch?v=eEuViHanjKI Use this or other procedures to start an arbitrary program at boot time. So ... ignore the fact that we are starting motion ... and start studying about how to start an arbitrary program at boot and we should be good | |
| May 15, 2016 at 18:18 | comment | added | gloaiza | Thank you @Kolban if I start it with <code>sudo /usr/bin/motion</code> It works, but I have to do this first: <code>sudo service motion stop</code> Now... How can I make it start on boot in this way...? | |
| May 15, 2016 at 4:38 | comment | added | Kolban | I'd suggest starting it from the command line instead of systemd and see if it reports any errors at the shell window. | |
| May 14, 2016 at 20:22 | review | First posts | |||
| May 15, 2016 at 7:48 | |||||
| May 14, 2016 at 20:22 | history | asked | gloaiza | CC BY-SA 3.0 |