Some things you can try:
  1. Check your autoinstall procedure, if you have one, for signs of the program. At UCI/NACS/DCS, see the "each" and "bin" and "lib" directories on autoinst
  2. Log into one or more machines you know is running the program, and:
    1. Try ps -ef | grep progname (or ps auxww | grep program). If it shows up in ps:
      1. See what arguments it's running with
      2. See if there's a hard path to where the program is located
      3. Try using a system call tracer on it, to see what it's up to
    2. Find the program:
      1. See above under "ps -ef"
      2. Try which and/or type -all, to locate the program
      3. type -all -path is good too, if you think there may be more than one version of the program on your path
      4. Try locate to find the program
    3. Once you've found the program, "file" it to see what kind of program it is. If it's a script, bring it up in a text editor. If it's a binary try "strings `which prog` | grep /" to see what pathnames it has an affinity to
    4. cd /etc, and run "find . -type f -print | xargs grep -il progname" to see what, if any, rc scripts or config files pertain to your program
    5. Try other forms of recursive search, including with and without xargs, to search both the content of files, and filenames. On a large system, you'll probably want to only search specific directories, but if the system is smaller than that, you can often search all filesystems, likely excluding NFS mounts.
  3. Google

Hits: 3103
Timestamp: 2024-03-01 12:02:37 PST

Back to Dan's tech tidbits

You can e-mail the author with questions or comments: