begin James Hook quotation: > > If you do find a way of getting the output from a process without doing > logging/screen please share, as every now and then theres a stray process > that I want to know what its doing/outputting. It won't do what you're asking, but it may do what you need: Package: strace Priority: standard Section: utils Installed-Size: 216 Maintainer: Wichert Akkerman <wakkerma@debian.org> Architecture: i386 Version: 4.4-1.2 Depends: libc6 (>= 2.2.3-7) Filename: pool/main/s/strace/strace_4.4-1.2_i386.deb Size: 72036 MD5sum: e1418909c3163549c226035b088a9275 Description: A system call tracer. strace is a system call tracer, i.e. a debugging tool which prints out a trace of all the system calls made by a another process/program. The program to be traced need not be recompiled for this, so you can use it on binaries for which you don't have source. . System calls and signals are events that happen at the user/kernel interface. A close examination of this boundary is very useful for bug isolation, sanity checking and attempting to capture race conditions. This is one of the ways to find out what a process is doing if you can't get a controlling terminal for it. -- Shawn McMahon | McMahon's Laws of Linux support: http://www.eiv.com | 1) There's more than one way to do it AIM: spmcmahonfedex, smcmahoneiv | 2) Somebody thinks your way is wrong
Attachment:
pgp7LDl6Ez4t7.pgp
Description: PGP signature