Dear all, I guess there is something I cannot see before my very eyes, so I hope you will be patient with me!
Here are the facts. I start lavrec from /opt/bin (I compiled the sources), and everything goes right (at least, lavrec works as expected). Sometimes I record TV programs from my satellite decoder at night, so I schedule the recording with "at", but... the system hangs. So I tried again and again, till I decided to try even with "at now" and the same command that works without "at" and the result is still that: the system hangs. Well, actually it doesn't really hands: the system load becomes suddenly so high that even killing the process is very difficult because the terminal is incredibly slow, so it take about a minute to issue "ps | grep" and then "kill". Did anyone else experienced something like this? Why does lavrec suck all of the system resources when invoked by "at"? Am I using "at" the wrong way? Best regards. -- Andrea ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mjpeg-users mailing list Mjpeg-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mjpeg-users
