Unlocking dreport Processes

[Fairlight]

At Thu, Feb 21, 2008 at 09:44:08AM -0600 or thereabouts, suspect Chris
Rendall was observed uttering:
> I am using the filepro cgi program.  Some processes are getting hung up
> and I have not figured out how.

Which version?  1.0 or 2.0?

As for figuring out how, you have to pick the right command that doesn't
redirect the command to /dev/null automatically.  Unfortunately, I seem to
recall they -all- did in the last version I worked with.  That may or may
not be overridable, but if you try appending your command with manual
redirects to the right file, you have a 50/50 chance of seeing what's going
on behind the scenes.  You'd `less` the file that you get as a result and
look at the screen output for clues.  Usually it's self-apparent.  Usually.

> I created a shell script to determine the dreport processes and used the
> kill -9 <pid>.

SIGKILL (-9) is a signal of last resort.  Always try SIGINT and SIGTERM
first.  Maybe even a SIGHUP before those.

mark->