 Questions and
Answers
Amy Rich
Q I'm on a Solaris machine running 5.8, and
I'm trying to capture some information with ps. Something keeps going
awry with a job in the middle of the night, and I want to verify which arguments
were passed to the command. I've been using ps -ef, but that seems to
truncate the output.
A /usr/bin/ps will pull up to 80 unmodified
characters straight from the kernel but stop there. The other caveat is that
/usr/bin/ps separates the arguments by spaces, so if you had embedded spaces
in the command line, it would be impossible to tell from looking at the ps
output.
If you've installed SUNWscpux (or SUNWscpu if you're not on a 64-bit machine),
you may want to try /usr/ucb/ps. If you give it enough w flags (they're cumulative),
/usr/ucb/ps auwww will show all args, as modified by the process and stored
in /proc. Programs like sendmail modify their arguments, though, so this may
not give you exactly what you're looking for, either.
Solaris 9 contains a program called pargs in SUNWesu/SUNWesux that will examine
a process or core file and print the program's arguments and environment variables
and values.
Q I'm running BIND 9.2.2, and I'm trying to
lock down security on my zones via the named.conf configuration file. I want
to ensure that transfers are only allowed from hosts that match a certain IP
and that have a matching TSIG key. I can easily do one or the other, but I can't
seem to AND them together. Here's a snippet of my config file:
include "keys.txt";
acl slaves {
10.2.1.1;
};
acl notslaves { ! slaves; };
options {
directory "/etc/named";
listen-on { 10.1
|
