Juuso Alasuutari <[EMAIL PROTECTED]> writes: > On Tuesday 22 January 2008 21:10:55 Bob Ham wrote: >> On Tue, 2008-01-22 at 20:58 +0200, Nedko Arnaudov wrote: >> > Bob Ham <[EMAIL PROTECTED]> writes: > <snip> >> > > Applications are already launched from a wrapper within lashd (what it >> > > terms the "loader".) It calls fork() and exec(). The only thing that >> > > needs to be done is to change stdout and stderr to point to a log file >> > > after calling fork() and before calling exec(). The appropriate place >> > > for the file would be the application's directory under the project >> > > directory. >> > >> > Not just that, I want to know what app outputed what. If their out goes >> > to common log file, we need prefixing. >> >> Each connected LASH client has its own directory under the main LASH >> project directory. By redirecting each client's output to a file in its >> client-specific directory, there would be no common log file. > > There's always the distant possibility that the log file's name matches the > client's data file's name, and if they're in the same directory things break. > What about "$project_root/$unique_client_id.log" instead of the client's > directory?
IMHO normal, global and single lashd log file will serve us better. -- Nedko Arnaudov <GnuPG KeyID: DE1716B0>
pgpKEI7EalWy4.pgp
Description: PGP signature
_______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
