Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsfeed.straub-nv.de!newsfeed.kamp.net!newsfeed0.kamp.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Greg Russell <me@invalid.org>
Newsgroups: comp.os.linux.misc
Subject: Re: ext3 filesize problem
Date: 3 Feb 2012 19:39:13 GMT
Lines: 25
Message-ID: <9p2rf0F4v8U1@mid.individual.net>
References: <9o11esFnm1U1@mid.individual.net> <jffm43$ieq$2@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net 46E8jjVf9GpkuVcHexFoIwBEK+eGQkDbYJXb8b47lw4hSWKsTr
Cancel-Lock: sha1:BPW677qikMWnW/Nzq/AIiGcyGzA=
User-Agent: Pan/0.133 (House of Butterflies)
Xref: x330-a1.tempe.blueboxinc.net comp.os.linux.misc:4087

On Sun, 22 Jan 2012 00:43:47 +0000, J G Miller wrote in
jffm43$ieq$2@dont-email.me :

...
> QUOTE
> 
>   Motion simply creates the timelapse film with a standard mpeg1
>   framerate.
> 
>   Note : maximum size for timelapse files is 2GB.
>    
> UNQUOTE
> 
>> It's difficult to imagine that "motion" would limit the size
> 
> Oddly enough I find it quite easy to imagine that.  ;)

You do? Thanks for the detective work as that explains the behaviour, but 
why motion should limit an mpeg file to 2GB is still not understandable 
to me, so I'll speak to the author(s) about it.

Other video files on the same filesystem are about 4.4GB, but motion's 
2GB filesize limit kills the program, destroying its usefulness for 
remote security documentation.