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: events cause zombie processes when using motion via
libcamerify (Dale Magee) (Mathias Koerber)
2. Re: events cause zombie processes when using motion via
libcamerify (Dale Magee) (Dale Magee)
3. Re: events cause zombie processes when using motion via
libcamerify (Dale Magee) (MrDave)
4. Re: events cause zombie processes when using motion via
libcamerify (Dale Magee) (Dale Magee)
----------------------------------------------------------------------
Message: 1
Date: Sat, 13 Apr 2024 21:37:20 +0800
From: Mathias Koerber <math...@koerber.org>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] events cause zombie processes when using
motion via libcamerify (Dale Magee)
Message-ID: <dafa6ac2-72b1-4938-b758-ac745bc4e...@koerber.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Dale Magee <antisol+mot...@antisol.org> asked:
> Hi,
>
> I'm hoping somebody might be able to help me track down this problem
> that appears to be an issue with either motion or libcamerify:
>
> https://github.com/Motion-Project/motion/issues/1522#issuecomment-2051560044
>
> This issue also links to the issues i've created on the libcamera
> github, and the relevant issue on the motioneye github.
There was a thread I started in february on this, which came to no
conclusion:
https://sourceforge.net/p/motion/mailman/message/58732180
My last guess there was:
> Could it be that motion inherits the signal setting from the libcamerify
> wrapper (which I guess might be set to ignore, so no wait ever take place?)
------------------------------
Message: 2
Date: Sun, 14 Apr 2024 14:08:42 +1000
From: Dale Magee <antisol+mot...@antisol.org>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] events cause zombie processes when using
motion via libcamerify (Dale Magee)
Message-ID: <ba6d905a-352b-4e86-9e26-702799003...@antisol.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Thanks for the response Mathias
Hmmm, so it seems that there are a few people having similar issues (see
also the github issue on the motioneye project that I found / linked to
previously)
I found a very old (2005!) discussion that looks similar, where the
problem was related to signals and eventually solved:
https://sourceforge.net/p/motion/mailman/motion-user/thread/20051111230017.2207da01.l4b9%40gmx.net/#msg6649816
And then again in 2010 there was a bsd user seeing a similar issue:
https://sourceforge.net/p/motion/mailman/message/25086836/
The fact that such a similar thing has been reported by multiple people
recently, and also cropped up in the past, makes me think that the issue
is with motion rather than libcamerify.
Could this be a regression of something fixed 19 years ago?
-Dale
On 13/4/24 23:37, Mathias Koerber wrote:
> Dale Magee <antisol+mot...@antisol.org> asked:
>> Hi,
>>
>> I'm hoping somebody might be able to help me track down this problem
>> that appears to be an issue with either motion or libcamerify:
>>
>> https://github.com/Motion-Project/motion/issues/1522#issuecomment-2051560044
>>
>> This issue also links to the issues i've created on the libcamera
>> github, and the relevant issue on the motioneye github.
>
> There was a thread I started in february on this, which came to no
> conclusion:
>
> ?? https://sourceforge.net/p/motion/mailman/message/58732180
>
> My last guess there was:
>
>> Could it be that motion inherits the signal setting from the
>> libcamerify wrapper (which I guess might be set to ignore,? so no wait
>> ever take place?)
>
>
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
Message: 3
Date: Sat, 13 Apr 2024 22:28:40 -0600
From: MrDave <motionmrd...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] events cause zombie processes when using
motion via libcamerify (Dale Magee)
Message-ID: <ed179f3e-88dc-454c-83c5-28dc2a219...@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Yea, so that 2005 patch/revision for SIGCHLD never made it into the main
code or was reverted.? From what I uncovered, that is the solution
however.? SIGCHLD needs to be trapped and then a wait() is needed to
acknowledge the child terminating.? My recent tests also show that
really two calls may be required to wait() to prevent all the zombies.?
(The need for two call to wait() could also be due to the test program
created).
MrDave
On 4/13/2024 10:08 PM, Dale Magee wrote:
> Thanks for the response Mathias
>
> Hmmm, so it seems that there are a few people having similar issues
> (see also the github issue on the motioneye project that I found /
> linked to previously)
>
> I found a very old (2005!) discussion that looks similar, where the
> problem was related to signals and eventually solved:
>
> https://sourceforge.net/p/motion/mailman/motion-user/thread/20051111230017.2207da01.l4b9%40gmx.net/#msg6649816
>
>
>
> And then again in 2010 there was a bsd user seeing a similar issue:
> https://sourceforge.net/p/motion/mailman/message/25086836/
>
> The fact that such a similar thing has been reported by multiple
> people recently, and also cropped up in the past, makes me think that
> the issue is with motion rather than libcamerify.
>
> Could this be a regression of something fixed 19 years ago?
>
> -Dale
>
>
> On 13/4/24 23:37, Mathias Koerber wrote:
>> Dale Magee <antisol+mot...@antisol.org> asked:
>>> Hi,
>>>
>>> I'm hoping somebody might be able to help me track down this problem
>>> that appears to be an issue with either motion or libcamerify:
>>>
>>> https://github.com/Motion-Project/motion/issues/1522#issuecomment-2051560044
>>>
>>>
>>>
>>> This issue also links to the issues i've created on the libcamera
>>> github, and the relevant issue on the motioneye github.
>>
>> There was a thread I started in february on this, which came to no
>> conclusion:
>>
>> ??? https://sourceforge.net/p/motion/mailman/message/58732180
>>
>> My last guess there was:
>>
>>> Could it be that motion inherits the signal setting from the
>>> libcamerify wrapper (which I guess might be set to ignore,? so no
>>> wait ever take place?)
>>
>>
>>
>> _______________________________________________
>> Motion-user mailing list
>> Motion-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> https://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
Message: 4
Date: Sun, 14 Apr 2024 15:32:58 +1000
From: Dale Magee <antisol+mot...@antisol.org>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] events cause zombie processes when using
motion via libcamerify (Dale Magee)
Message-ID: <953a1bf3-e488-4063-8edf-b90d02250...@antisol.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Omg this is great progress! Thank you so much for looking into it!
Is there anything I can do to help? I could probably figure out how to
compile and test it if you want to point me at a branch/commit to check out?
Again, thanks so much!
-Dale
On 14/4/24 14:28, MrDave wrote:
> Yea, so that 2005 patch/revision for SIGCHLD never made it into the main
> code or was reverted.? From what I uncovered, that is the solution
> however.? SIGCHLD needs to be trapped and then a wait() is needed to
> acknowledge the child terminating.? My recent tests also show that
> really two calls may be required to wait() to prevent all the zombies.
> (The need for two call to wait() could also be due to the test program
> created).
>
> MrDave
>
> On 4/13/2024 10:08 PM, Dale Magee wrote:
>> Thanks for the response Mathias
>>
>> Hmmm, so it seems that there are a few people having similar issues
>> (see also the github issue on the motioneye project that I found /
>> linked to previously)
>>
>> I found a very old (2005!) discussion that looks similar, where the
>> problem was related to signals and eventually solved:
>>
>> https://sourceforge.net/p/motion/mailman/motion-user/thread/20051111230017.2207da01.l4b9%40gmx.net/#msg6649816
>>
>> And then again in 2010 there was a bsd user seeing a similar issue:
>> https://sourceforge.net/p/motion/mailman/message/25086836/
>>
>> The fact that such a similar thing has been reported by multiple
>> people recently, and also cropped up in the past, makes me think that
>> the issue is with motion rather than libcamerify.
>>
>> Could this be a regression of something fixed 19 years ago?
>>
>> -Dale
>>
>>
>> On 13/4/24 23:37, Mathias Koerber wrote:
>>> Dale Magee <antisol+mot...@antisol.org> asked:
>>>> Hi,
>>>>
>>>> I'm hoping somebody might be able to help me track down this problem
>>>> that appears to be an issue with either motion or libcamerify:
>>>>
>>>> https://github.com/Motion-Project/motion/issues/1522#issuecomment-2051560044
>>>>
>>>> This issue also links to the issues i've created on the libcamera
>>>> github, and the relevant issue on the motioneye github.
>>>
>>> There was a thread I started in february on this, which came to no
>>> conclusion:
>>>
>>> ??? https://sourceforge.net/p/motion/mailman/message/58732180
>>>
>>> My last guess there was:
>>>
>>>> Could it be that motion inherits the signal setting from the
>>>> libcamerify wrapper (which I guess might be set to ignore,? so no
>>>> wait ever take place?)
>>>
>>>
>>>
>>> _______________________________________________
>>> Motion-user mailing list
>>> Motion-user@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/motion-user
>>> https://motion-project.github.io/
>>>
>>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>>
>>
>> _______________________________________________
>> Motion-user mailing list
>> Motion-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/motion-user
>> https://motion-project.github.io/
>>
>> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
>
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
------------------------------
------------------------------
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 212, Issue 13
********************************************
