On Thu, 2003-09-18 at 16:44, Net Llama! wrote: > > yes, that's the load at the instant that you ran the command. were you > attempting to encode a wav when you ran that? if so, then the load > appears to be fine. you might want to just run 'top' the entire time to > see what is going on across the board (cpu, memory, load).
It is at all possible that this is a memory issue? With a file that big, if your audio application tries to fit it all in memory, and you only have 256MB and a correspondingly small swap file, then it may be running out and truncating the file. I know with graphics files this can happen... just a thought, YMMV -- burns _______________________________________________ Linux-users mailing list [EMAIL PROTECTED] Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
