🚀 go-pugleaf

In article <10314@medusa.cs.purdue.edu> df@sei.cmu.edu (Dan Farmer) writes:
>  Sorry to get in on this conversation late, but feel free to send
>any comments, mods, diffs, flames, whatever straight to me.  I've barely
>gotten any response from the net, so I don't know if people are using COPS,
>having problems with installation, want more features, or what.  I plan
>on continuing work on it, so if you want to say something, now's the time....
>  High on my list of things to do include:
>
>   Better installation, configuration (do I hear Larry's Config calling?)
>   An easy filtering mechanism to get rid of unwanted output
>   More uucp, nfs, yp checks.
>   And of course, crushing any bugs and eliminating as many port problems
>	as possible.
>
>  Also, I'd like to solicit responses on how people feel about a similar
>tool to look for bugs (sendmail, etc.)  COPS II?
>  df@sei.cmu.edu
>df@medusa.cs.purdue.edu

	I have attempted to use it on 386/ix v2.0.1.  I compiles with only
minimal fixes to the makefile, but it just won't run.  Some piece dumps core
and leaves no trace.  Another piece runs forever without producing anything.
Given the press of time, I have read through the code somewhat and have 
checked several things by hand.

	Thanks for the effort, it looks like a good concept.
-- 
Gregory G. Woodbury @ The Wolves Den UNIX, Durham NC
UUCP: ...dukcds!wolves!ggw   ...mcnc!wolves!ggw           [use the maps!]
Domain: ggw@cds.duke.edu     ggw%wolves@mcnc.mcnc.org
[The line eater is a boojum snark! ]           <standard disclaimers apply>