Re: [Condor-users] writing hawkeye modules

[Nick LeRoy <nleroy@xxxxxxxxxxx>]

On Tue February 7 2006 2:07 am, obi wrote:
> On Mon, Feb 06, 2006 at 10:29:24PM -0600, Nick LeRoy wrote:
> > In the StartLog, you should see messages something like this (Make sure
> > you have D_FULLDEBUG) turned on:
>
> My apologies to be so dense: where should I turn D_FULLDEBUG on? I found
> at least 2 instances of it in the config file (STORK, CREDD and QUILL I
> think). Is there a STARTD_DEBUG?

Yup, your STARTD_DEBUG will probably be something like this (after you add the 
D_FULLDEBUG):

STARTD_DEBUG = D_COMMAND D_FULLDEBUG

> > 2/6 22:16:35 Cron: 'NWS' (pid 10318) exit_status=0
> > 2/6 22:16:35 NWS: 51 lines in Queue
> > 2/6 22:16:35 Replacing ClassAd for 'NWS'
> > 2/6 22:16:35 Cron: STDOUT closed for 'NWS'
> > 2/6 22:16:35 Cron: STDERR closed for 'NWS'
>
> Definetely not in the logs ...

Those are probably only printed for D_FULLDEBUG (checking...)  Indeed, these 
messages are all D_FULLDEBUG.

> I had another command complain loudly about the input (and now I
> understand why) and everything was in the log. There is nothing with cat.
> And no cat in the list of process (in case it got stuck there).
>
> I'll try harder tomorrow.

See if the above helps..

-Nick

-- 
           <<< Knock, knock, Neo. >>>
 /`-_    Nicholas R. LeRoy               The Condor Project
{     }/ http://www.cs.wisc.edu/~nleroy  http://www.cs.wisc.edu/condor
 \    /  nleroy@xxxxxxxxxxx              The University of Wisconsin
 |_*_|   608-265-5761                    Department of Computer Sciences