Send Motion-user mailing list submissions to motion-user@lists.sourceforge.net
To subscribe or unsubscribe via the World Wide Web, visit https://lists.sourceforge.net/lists/listinfo/motion-user or, via email, send a message with subject or body 'help' to motion-user-requ...@lists.sourceforge.net You can reach the person managing the list at motion-user-ow...@lists.sourceforge.net When replying, please edit your Subject line so it is more specific than "Re: Contents of Motion-user digest..." Today's Topics: 1. Re: I'm screwing something up, but what?.. (JB) 2. Re: I'm screwing something up, but what? <SOLVED...hopefully> (JB) ---------------------------------------------------------------------- Message: 1 Date: Wed, 22 Apr 2020 14:08:29 -0500 From: JB <yona...@riseup.net> To: motion-user@lists.sourceforge.net Subject: Re: [Motion-user] I'm screwing something up, but what?.. Message-ID: <20200422140829.6ea1fcd4@ACAB.TOSIAR> Content-Type: text/plain; charset=US-ASCII On Wed, 22 Apr 2020 23:39:36 +1200 greg thomas <geete...@gmail.com> wrote: > My uneducated guess is that you seem to have used the ';' character to > comment out various parameters including the Netcam ones, but I suspect > motion is still parsing these and is possibly not handling the value pairs > directly. Try using the '#' character instead to remove the parameters your > not using. > > Just a thought...... > > Good idea! Thanks! I'll try it as soon as I can and let the list know what happened. JB ------------------------------ Message: 2 Date: Wed, 22 Apr 2020 17:58:56 -0500 From: JB <yona...@riseup.net> To: motion-user@lists.sourceforge.net Subject: Re: [Motion-user] I'm screwing something up, but what? <SOLVED...hopefully> Message-ID: <20200422175856.7fc25f2b@ACAB.TOSIAR> Content-Type: text/plain; charset=US-ASCII On Tue, 21 Apr 2020 19:16:50 -0500 JB <yona...@riseup.net> wrote: > Hi folks, > <big SNIP> Okay, it seems that I was getting ahead of myself when I was watching the log file *size* grow over what I was used to with Motion 4.2.2. With that version, when I'd start Motion, no matter with one camera or more than one, the log file *size* would pop up at 172 kb and remain there. With 4.3.1, I saw it go from 172kb to 385kb and I would hit my Motion stop real fast so that the log wouldn't keep growing and growing. It seems that the log file *size* actually *stopped* at 385kb, and even with one or more cameras running the line 'motion_init: Substream not available. Image sizes not modulo 16' is there for *all* cameras that Motion is running. I still have no clue what that line means, but it doesn't seem to be hurting anything and my Motion is working as it's supposed to. So apparently it was just *ME* jumping the gun and worrying, probably because I wanted to make sure the Motion build I'd made for Slackware was working correctly. As for that...I tried to contact the maintainer for Motion on Slackware and it seems his e-mail address is no longer in service. So, I'll see if I can get any volunteers to test my build on their 14.2 x64 systems (I'll ask on LinuxQuestions.org) and if it does okay for them also, I'll actually see if I can maintain the package for Slackware. As it stands though, at least on my Slackware 14.2 x64 system, Motion 4.3.1 is working just fine. I'm sorry for the large e-mails and junk people skimmed through to try and help, but I guess that's all a part of 'debugging', in a way. Anyway, thanks to all who offered suggestions. JB ------------------------------ ------------------------------ Subject: Digest Footer _______________________________________________ Motion-user mailing list Motion-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/motion-user ------------------------------ End of Motion-user Digest, Vol 166, Issue 24 ********************************************