Hey, ok, I see where you're coming from now
Actually, if you don't know where a particular process logs to, figuring that out from the process itself can be done, but it's not necessarily simple (although, hey, sometimes it is).
I would suggest that you do the log search prior to killing the PIDS associated with the process. Probably the best tools to use (although they may be a bit bulky) would be "lsof" or "truss" ("strace, xtrace, etc, all the same pretty much - depends on your distro of Linux or Unix).
In lsof you could do a simple
and then sift through that output to find any open files associated with the process (eyeball it first and then script the grep out)
for truss, strace, xtrace, etc try doing (I'll use truss for an example, but check the man page for whatever statement-tracing or execution tracing software your distro comes with:
truss -f -p PID|egrep -i 'open|read|write|close'
and check out what files it opens and writes to and then script that out, after watching it manually.
Hopefully that helps. It might be difficult to get it, but it can be done. And, like I said, it might be really simple.
Oh, yes, one last thing - if you know the location of the program, you can run "strings" against it and probably find out where it logs to from that output:
strings /full/path/to/dyyno
Best wishes,
Miek
Unsolved 
Offline 
