>I'm seeing the following type of output in my logs:
>
>From [ANONYMOUS]@LISTSERV.VT.EDU: X-LOGCK [18 cookie chars elided]
>AUTHINFO(IP address elided) ORGINFO(IP address elided) GETCFG (...)
>
>Upshot - for IPv4, only 10 useful chars of command get logged:
>
>0.3) WM: LISTS  (...)
>0.3) OWNER(ENGR (...)
>0.3) OWNER(ENGR (...)
>0.3) OWNER(SOPH (...)
>
>Not exactly the most helpful for debugging/tracing.  If it's going to log 120
>chars *anyhow*, is there any way to get it to go to 130 and log 20 chars of
>command? (Yes, I see that hard-coded "%T From %s: %.80s (...)%w" format string
>in the lsv binary. ;)
>
>Alternately, is there any real purpose to logging both authinfo and orginfo
>values? Checking back through the last month's logs, I have 517,306 X-LOGCK
>entries from 45,256 different IP's. Of the 2,478 of which had
>AUTHINFO in them,
>all the IPv4 addresses had identical auth and org values, which implies that
>logging origininfo is pointless if we have an authinfo value, unless there's a
>corner case where the two values don't match.
>
>For ipv6, it's totally useless:
>
>X-LOGCK (cookie elided)
>AUTHINFO(2001:468:c80:2103:224:e8ff:fec6:ad17) ORGINF (...)
>
>Gaah. ;)
>
>It doesn't even get the origininfo out, much less log the command.

Try setting DEBUG_LOG_TCPGUI to 1:
<http://www.lsoft.com/manuals/16.0/sitevars.html#cDebuglogtcpgui>  I
think that should do the trick.

Thanks,
--
Jacob Haller, Technical Support, L-Soft international, Inc
   LISTSERV (R) is a registered trademark of L-Soft.
    Support is available 9:00-18:00 ET, Monday-Friday
     except on the following holidays:
      <http://www.lsoft.com/resources/holidays.asp>

L-Soft's LISTSERV(R) Choice Awards - The Mailys: Nominate and Vote
Today:  http://www.lsoft.com/news/choiceawards.asp

Got the latest LISTSERV version? Upgrade now to LISTSERV 16.0:
http://www.lsoft.com/products/listserv_160.asp