On Tue, 10 Feb 2004, Dragon_at_work wrote:
> > ARG_MAX has nothing to do with it - you're only passing 1 file argument
>
> I have over 12G free (about 200MB free RAM) and I am getting return codes of
> 32512 from system calls that try to deal with all 1066 files yuv'ing them. It
> goes ahead for 805 files (command string length of 129620), but nothing
> higher.
>
> Any ideas? I figure it is something simple that I am overlooking....
How are you processing the files? If you are doing something like
this:
command file1 file2 file3 file4 ... file1066 | mpeg2enc ...
then yes, there is a system imposed limit of ARG_MAX.
On the other hand, if you do something like this:
(command file1; \
command file2 | skip1; \
...
command file1066 | skip1 ) | mpeg2enc
[where 'skip1' is either a shell function or another script to
remove the YUV4MPEG2 header and pass the remainder of the stream
thru]
then the limit is the amount of space (and your patience for the
shell to parse the script ;)) available.
It sounds like you're passing all the filenames as arguments to
a single "convert from jpeg to yuv4mpeg" command rather than using
multiple convert commands each with but a single argument.
Cheers,
Steven Schultz
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Mjpeg-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/mjpeg-users
