Send Motion-user mailing list submissions to
        [email protected]

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
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."


Today's Topics:

   1. Re: suppressing error messages (Kaiwan N Billimoria)
   2. Re: suppressing error messages (tosiara)
   3. Re: Suggestion for IP CAM (Markus Tobatz)


----------------------------------------------------------------------

Message: 1
Date: Mon, 12 Jul 2021 08:40:56 +0530
From: Kaiwan N Billimoria <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] suppressing error messages
Message-ID:
        <CAPDLWs_3FNA=P5pTycGnxwRU7UA3co=8nvyjexcfv_hftk9...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

One approach, perhaps: as the objective is to reduce writes to the disk
media, you
could redirect all logs to a RAM-based filesystem - /tmp or /run (or
/dev/shm) are typically mounted as tmpfs.

>From there, you could use a simple script to filter out the particular
messages you don't want and save the result
to the actual disk partition.

HTH,
Kaiwan.

On Sat, Jul 10, 2021 at 7:03 AM S Andreason <[email protected]> wrote:

> In an effort to reduce the number of write cycles to my Pi boot SD-card,
> I added a SSD USB drive. After reformatting to ext4 failed with
> recurring corrupted superblock, I have fallen back to exfat.
>
> Can I suppress these _specific_ error messages? without turning off the
> ERR level of reporting?
>
> [1:ml1:205_HikVisi] [ERR] [EVT] [Jul 09 18:24:00] event_image_snapshot:
> Could not create symbolic link [20210709-snapshot.jpg]: Function not
> implemented
> repeated every minute.
>
> Thanks,
> Stewart
>
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
>
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 2
Date: Mon, 12 Jul 2021 13:30:23 +0300
From: tosiara <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] suppressing error messages
Message-ID:
        <cachtdwqytyjbve-swwsayheb8-bscjrqmbhzj6pvm2vsj2b...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Try to set "snapshot_filename lastsnap"this should avoid creating symlink
https://motion-project.github.io/motion_config.html#snapshot_filename

On Mon, Jul 12, 2021 at 6:12 AM Kaiwan N Billimoria <
[email protected]> wrote:

> One approach, perhaps: as the objective is to reduce writes to the disk
> media, you
> could redirect all logs to a RAM-based filesystem - /tmp or /run (or
> /dev/shm) are typically mounted as tmpfs.
>
> From there, you could use a simple script to filter out the particular
> messages you don't want and save the result
> to the actual disk partition.
>
> HTH,
> Kaiwan.
>
> On Sat, Jul 10, 2021 at 7:03 AM S Andreason <[email protected]> wrote:
>
>> In an effort to reduce the number of write cycles to my Pi boot SD-card,
>> I added a SSD USB drive. After reformatting to ext4 failed with
>> recurring corrupted superblock, I have fallen back to exfat.
>>
>> Can I suppress these _specific_ error messages? without turning off the
>> ERR level of reporting?
>>
>> [1:ml1:205_HikVisi] [ERR] [EVT] [Jul 09 18:24:00] event_image_snapshot:
>> Could not create symbolic link [20210709-snapshot.jpg]: Function not
>> implemented
>> repeated every minute.
>>
>> Thanks,
>> Stewart
>>
>>
>> _______________________________________________
>> Motion-user mailing list
>> [email protected]
>> 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
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 3
Date: Mon, 12 Jul 2021 12:42:22 +0200
From: Markus Tobatz <[email protected]>
To: Motion discussion list <[email protected]>
Subject: Re: [Motion-user] Suggestion for IP CAM
Message-ID:
        <cab9jkdb3mlhsyrt6vtpdylcwu7yahvi6fwmdajjrq_irkz6...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

That's interesting. My CPU supports Intel Quick Sync/H265, but will Motion
support it too?

Am Sa., 10. Juli 2021 um 17:10 Uhr schrieb S Andreason <[email protected]
>:

> Hi Markus,
> Check the camera's video encoding setting, H264 uses less CPU to decode
> than H265/HEVC.
> and of course, the higher the resolution, the slower things will go.
>
>
> Markus Tobatz wrote:
> >  RTSP stream in FullHD and that resulted in 90% CPU usage just for
> > that one camera)
>
>
>
> _______________________________________________
> Motion-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------



------------------------------

Subject: Digest Footer

_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user


------------------------------

End of Motion-user Digest, Vol 181, Issue 7
*******************************************

Reply via email to