Well, the way I did it here works, but is not as exciting or "correct" as your suggestion; I use mp1e, so I wrapped it in a shell script that accepts the arguments that you would normally pass to mencoder. The shell script touches and removes the file, so even though the 'record_daemon' doesn't manage the lockfile, the interface still knows about it.
On Mon, Feb 24, 2003 at 10:35:16PM -0600, Krister Lagerstrom wrote: > Not a bad idea. It isn't real easy to implement though since it isn't > known now when the recording program is done. It would have to be run > in a child process, but that is probably a good idea anyway for easy > killing. Especially if we make the recording daemon a real daemon that > is always alive, and handles requests through RPC from Freevo and the > web tools. ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel