Date: | Fri, 12 Jun 2015 10:05:51 -0500 |
---|---|
From: | Greg Thain <gthain@xxxxxxxxxxx> |
Subject: | [HTCondor-devel] new D_FULLDEBUG DAEMONCORE dprintf messages |
All:I notice that at D_FULLDEBUG, we are getting a bunch of new messages around every daemon core command: 06/11/15 14:30:37 Return from Timer handler 8 (Time to negotiate) 06/11/15 14:30:37 DAEMONCORE: ReadCommand() 06/11/15 14:30:37 DAEMONCORE: EnableCrypto() 06/11/15 14:30:37 DAEMONCORE: VerifyCommand() 06/11/15 14:30:37 DAEMONCORE: SendResponse() 06/11/15 14:30:37 DAEMONCORE: SendResponse() : NOT m_new_session06/11/15 14:30:37 DAEMONCORE: ExecCommand(m_req == 421, m_real_cmd == 421, m_auth_cmd == 421) 06/11/15 14:30:37 Calling HandleReq <RESCHEDULE_commandHandler> (0) for command 421 (Reschedule) from unauthenticated@unmapped <128.105.14.141:34248> Do these need to be D_FULLDEBUG? -greg |
[← Prev in Thread] | Current Thread | [Next in Thread→] |
---|---|---|
|
Previous by Date: | , (nil) |
---|---|
Next by Date: | [HTCondor-devel] Socket changes in 8.3.2, Ben Cotton |
Previous by Thread: | Re: [HTCondor-devel] DaemonCore ChildAlive & systemd/docker/etc?, Brian Bockelman |
Next by Thread: | [HTCondor-devel] python bindings: why linux only?, Erik Paulson |
Indexes: | [Date] [Thread] |