On 4/9/2008 [EMAIL PROTECTED] wrote: > From the command line, you should be able to type "set" to see what's > in your current environment. All of those values will be passed to > any program you run.
Thank you. That did it. > To see the environment for a running process, it's a bit more > challenging. Some Unixes make it easier to view the environment of a > running process by interrogating the kernel. For example, in Linux > you > can just read /proc/$PID/environ to see the environment for a process > with a pid of $PID. This file is Linux-specific however, so the BSD, > Mac OS X, Solaris, etc will all have different techniques. If the > kernel doesn't expose the information the way Linux does, you may > have > to use some kind of debugger like gdb or strace to view the process' > information. Ahhh, now I get it. I simply presumed that a running process could read 'the environment' and there is only one 'environment'. So each process has its own environment, too. Cute. Now your argument against using the environment for too much, makes better sense to me. Thanks, Bucky _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
